Hi Michael,
On Sat, Mar 22, 2014 at 2:32 AM, schmitz
<schmitz@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
That's not true. E.g. I/O memory is never mapped by mem_init().
Why, then, does the ioremap() of ST-RAM fail? Because the physical
address
is lower than the lowest currently mapped physical address?
I don't know. How does it fail?
Example:
Unable to handle kernel access at virtual address 5f435059
Oops: 00000000
Modules linked in:
PC: [<00089552>] kmem_cache_alloc+0x12/0x9a
SR: 2700 SP: 0029dec0 a2: 002a42d8
d0: 000080d0 d1: 00000013 d2: 000080d0 d3: 0007fe3c
d4: 00000001 d5: 000000d0 a0: 5f435055 a1: 002a75ee
This may be too early in the boot process to call ioremap().
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
