From: Marco Stornelli <marco.stornelli@gmail.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Yuasa Yoichi <yuasa@linux-mips.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Embedded <linux-embedded@vger.kernel.org>
Subject: Re: [PATCH v2] char drivers: Ram oops/panic logger
Date: Sat, 13 Mar 2010 09:49:53 +0100 [thread overview]
Message-ID: <4B9B51B1.8010904@gmail.com> (raw)
In-Reply-To: <20100312233144.GG6491@shareable.org>
Il 13/03/2010 00:31, Jamie Lokier ha scritto:
> That'd be fine if the kernel link scripts choose the address, as long
> as it's consistent between different compiles and similar
> configurations. That'd be a bit simpler than the admin having to know
> the memory map well enough to choose an address.
>
> -- Jamie
>
I agree, but the bootloader should be aware of it. I mean, usually
bootloaders at boot, reset the RAM, so you have to tell to the
bootloader that you are using a piece of RAM as persistent RAM, for
example U-Boot has got a specific option CONFIG_PRAM. I don't know if
all the process can be completely transparent to the admin in all
situations.
Marco
next prev parent reply other threads:[~2010-03-13 8:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 17:41 [PATCH v2] char drivers: Ram oops/panic logger Marco Stornelli
2010-03-10 2:08 ` Yuasa Yoichi
2010-03-10 8:02 ` Marco Stornelli
2010-03-10 9:20 ` Yuasa Yoichi
2010-03-10 12:15 ` Marco Stornelli
2010-03-12 22:48 ` Andrew Morton
2010-03-12 23:31 ` Jamie Lokier
2010-03-13 8:49 ` Marco Stornelli [this message]
2010-03-15 3:09 ` Jamie Lokier
2010-03-15 8:11 ` Marco Stornelli
2010-03-13 8:50 ` Marco Stornelli
2010-03-13 14:50 ` Geert Uytterhoeven
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=4B9B51B1.8010904@gmail.com \
--to=marco.stornelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jamie@shareable.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuasa@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.