Re: [PATCH] ramoops appears geared to not support ARM
From: Marco Stornelli
Date: Tue Nov 01 2011 - 04:58:35 EST
Il 01/11/2011 00:03, Bryan Freed ha scritto:
On Mon, Oct 31, 2011 at 1:57 AM, Marco Stornelli
And I cannot shake the feeling that we have a fairly simple disconnect
here. Ramoops expects to use _device_ memory because it uses
ioremap(). But the buffer itself is accessed through /dev/mem which
(as we use it with no mmap() calls) expects to give access to _system_
no mmap calls?! I don't understand how you are using /dev/mem.
open(), lseek(), read(). No mmap is required for RAM, right?
dd if=/dev/mem bs=1 count=1000 skip=32M
Mmmm, the operations done are different. Try: reserve the memory with
memblock_reserve and read some data with this useful program
http://free-electrons.com/pub/mirror/devmem2.c from the right location
(the address used for ramoops).
Let me know.
Marco
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/