| To: | Jun Sun <jsun@mvista.com> |
|---|---|
| Subject: | Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA] |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Tue, 18 Dec 2001 17:30:15 -0200 |
| Cc: | jim@jtan.com, linux-mips@oss.sgi.com |
| In-reply-to: | <3C1F868C.492E155B@mvista.com>; from jsun@mvista.com on Tue, Dec 18, 2001 at 10:10:20AM -0800 |
| References: | <20011217151515.A9188@neurosis.mit.edu> <20011217193432.A7115@dea.linux-mips.net> <20011218020344.A10509@neurosis.mit.edu> <3C1F868C.492E155B@mvista.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
On Tue, Dec 18, 2001 at 10:10:20AM -0800, Jun Sun wrote: > It seems like i82365.c implies a PCI device. If this is true, then things do > make sense here. > > Just setting iomem_resource.end to 0xffffffff should get you by resource range > problem. Certainly not as that is the default. > It has nothing to isa_slot_offset here. I don't know about the history of > isa_slot_offset, but it appears to be faint effort to allow the access to what > is called "ISA memory" space on PC. This region, if it ever exists, should > never be a separate region on a MIPS machine. It should just be the beginning > part of PCI Memory space. > > Ralf, we should just delete isa_slot_offset to avoid any further confusions. No way as long as there are (E)ISA systems :-( Ralf |
| Previous by Date: | Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA], Jun Sun |
|---|---|
| Next by Date: | Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA], Ralf Baechle |
| Previous by Thread: | Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA], Jun Sun |
| Next by Thread: | Re: [ppopov@mvista.com: Re: [Linux-mips-kernel]ioremap & ISA], Geert Uytterhoeven |
| Indexes: | [Date] [Thread] [Top] [All Lists] |