[PATCH/RFC] Add Alternative Log Buffer Support for printk Messages

Matt Sealey matt at genesi-usa.com
Wed Nov 26 06:01:15 EST 2008


On Tue, Nov 25, 2008 at 12:55 PM, Josh Boyer <jwboyer at linux.vnet.ibm.com>wrote:

> On Tue, 25 Nov 2008 12:53:12 -0600
> "Matt Sealey" <matt at genesi-usa.com> wrote:
>
> > Nitpick, really.. shouldn't the logbuffer location(s) be some device tree
> > property(ies), perhaps something in the
> > /chosen node that U-Boot etc. can then fill out?
>
> I don't think that's a nitpick.  It's a fundamental change in how this
> would all work.  However, I do think you're generally right.
>
> Perhaps not /chosen, but maybe something like /rtas or /firmware, etc.
>
> josh


I think the best place is chosen, with things like stdin, stdout etc. - this
is where you generally go and dump weird little variables which need to be
passed in for early boot. You could consider the log buffer a kind of
stdin/out variation.

I don't think it needs a whole new device tree node just for two memory
locations.. is the support really worth a compatible property, etc. to
differentiate between different operating modes?

-- 
Matt Sealey <matt at genesi-usa.com>
Genesi, Manager, Developer Relations
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20081125/8bf8068e/attachment.htm>


More information about the Linuxppc-dev mailing list