Re: Making use of the BigRamPlus?
On Tue, Dec 17, 2013 at 9:17 AM, Ingo Jürgensmann <ij@2013.bluespice.org> wrote:
> modprobe phram phram=bigram,0x05000000,256Mi
> spice:/home/ij# cat /proc/mtd
> dev: size erasesize name
> mtd0: 10000000 00001000 "bigram"
>
> But when mkswap /dev/mtd0 I get this:
>
> Dec 17 07:59:06 spice kernel: [ 440.710000] phram: bigram device:
> 0x10000000 at 0x5000000
> Dec 17 07:59:47 spice kernel: [ 480.410000] Unable to handle kernel access
> at virtual address d0180000
You're sure 0x5000000 is the right address? cat /proc/iomem or lszorro -v will
tell you.
Still, the exception means that there's nothing mapped at the accessed address,
so either phram is using the wrong address, or we have a bug in ioremap().
Adding "#define DEBUG" at the top of arch/m68k/mm/kmap.c may give a hint.
I don't have any Z3 devices myself, but we do have users of Z3 graphics cards,
right?
I had a look at phram.c, but I don't see anything that's obviously wrong
(it should use memcpy_{from,to}io() instead of plain memcpy() for portability,
but that doesn't matter on m68k).
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
Reply to: