linux-mips
[Top] [All Lists]

Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA]

To: jim@jtan.com
Subject: Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA]
From: Jun Sun <jsun@mvista.com>
Date: Tue, 18 Dec 2001 11:09:10 -0800
Cc: Ralf Baechle <ralf@oss.sgi.com>, linux-mips@oss.sgi.com
References: <20011217151515.A9188@neurosis.mit.edu> <20011217193432.A7115@dea.linux-mips.net> <20011218020344.A10509@neurosis.mit.edu> <3C1F868C.492E155B@mvista.com> <20011218134536.A11726@neurosis.mit.edu>
Sender: owner-linux-mips@oss.sgi.com
Jim Paris wrote:
> 
> > It seems like i82365.c implies a PCI device.  If this is true, then things 
> > do
> > make sense here.
> 
> No, the VG469 (and original i82365) is most definately an ISA device.
> From the manual: "The VG-469 has built in a standard ISA interface ..."
> My machine, as much as I hate it, _does_ have an ISA bus located at
> isa_slot_offset.
> 

Really?!

Hmm, how does the driver access ISA memory area?  I did not find ioremap() nor
readb/writeb stuff.  Usually those two macros are used to access PCI memory
space.  That is the reason I said "the driver implies a PCI device".

If it is purely ISA driver, may it should use isa_read/isa_write macros, in
which case we can make use of isa_slot_offset (maybe isa_slot_offset is useful
after all. :-0)

Jun

<Prev in Thread] Current Thread [Next in Thread>