[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100315030945.GS6491@shareable.org>
Date: Mon, 15 Mar 2010 03:09:45 +0000
From: Jamie Lokier <jamie@...reable.org>
To: Marco Stornelli <marco.stornelli@...il.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Yuasa Yoichi <yuasa@...ux-mips.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Linux Embedded <linux-embedded@...r.kernel.org>
Subject: Re: [PATCH v2] char drivers: Ram oops/panic logger
Marco Stornelli wrote:
> 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.
Sometimes you can't change the bootloader (they don't always come with
source code). Or you could, but you don't want to risk it (there
isn't always a way to recover if you break it).
Obviously then the feature is only useful when the bootloader doesn't
clear all the RAM :-)
On slow boards in consumer devices, they sometimes avoid clearing the
RAM because that adds measurable boot time.
-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists