From: Marco Stornelli <marco.stornelli@gmail.com>
To: Bryan Freed <bfreed@chromium.org>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
msb@chromium.org, seiji.aguchi@hds.com
Subject: Re: [PATCH] ramoops appears geared to not support ARM
Date: Tue, 01 Nov 2011 09:52:29 +0100 [thread overview]
Message-ID: <4EAFB34D.8080807@gmail.com> (raw)
In-Reply-To: <CAEYUcX3dzG_DCBSj570qGoeM00NhjCBHLS7sLKvDw2jvUJnjVg@mail.gmail.com>
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
prev parent reply other threads:[~2011-11-01 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 23:21 Bryan Freed
2011-10-28 23:21 ` [PATCH] ramoops: Add support for ARM systems Bryan Freed
2011-10-29 8:39 ` [PATCH] ramoops appears geared to not support ARM Marco Stornelli
2011-10-29 9:34 ` Russell King - ARM Linux
2011-10-29 11:04 ` Marco Stornelli
2011-10-29 11:55 ` Russell King - ARM Linux
2011-10-29 12:42 ` Marco Stornelli
2011-10-29 12:53 ` Russell King - ARM Linux
2011-10-29 14:22 ` Marco Stornelli
[not found] ` <CAEYUcX1PUgniJLqYXKM5pf_9T06OPFg4q0ZUCFc8Deu1J_R9-A@mail.gmail.com>
2011-10-30 11:33 ` Marco Stornelli
2011-10-31 6:03 ` Bryan Freed
2011-10-31 8:57 ` Marco Stornelli
2011-10-31 23:03 ` Bryan Freed
2011-11-01 8:52 ` Marco Stornelli [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EAFB34D.8080807@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bfreed@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=msb@chromium.org \
--cc=seiji.aguchi@hds.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome