On Tue, 18 Dec 2001, Jim Paris wrote:
> > Therefore:
> >
> > set_io_port_base(0xb4000000);
> > isa_slot_offset = 0xb0000000;
>
> Yep, that's what I have.
>
> > > > -more /proc/iomem
> > > 00000000-00ffffff : System Ram
> > > 00002000-001bc6af : Kernel code
> > > 001cf300-00299fff : Kernel data
> > > (this seems very wrong to me, since the kernel is most definately
> > > not in the I/O memory space; real memory, of course, but I/O memory??)
> >
> > No, this makes perfect sense on a 16mb system.
>
> How so? See the memory map I just sent in my other mail. Should I be
> adding isa_slot_offset to calls to check/request/release_mem_region?
> Or should I make a isa_{check,request,release}_mem_region that adds
> this in? In which case, doesn't that turn /proc/iomem into a general
> memory map rather than an I/O memory map?
IMHO you should create isa_{check,request,release}_mem_region().
I said it many times before on linux-kernel, but it doesn't help :-(
I'm facing the same problem on PPC, where ISA memory space is not at address 0.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
