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

["Matt Sealey" <matt@genesi-usa.com>]

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

On Tue, Nov 25, 2008 at 3:05 PM, Wolfgang Denk <wd@denx.de> wrote:

> Dear Matt,
>
> In message <b5e2fc790811251131g63ea9444x57ec0829ca0b069e@mail.gmail.com>
> you wrote:
> >
> > There is also no reason you can't hard-code the locations into the device
> > tree, to support older U-Boots that don't know about
> > /chosen/linux,log-metadata and /chosen/linux,log-buffer*.
>
> Actually there is such reason - U-Boot traditionally allocates the log
> buffer close to the upper end of system memory, so the start address
> depends on the memory size on the board, which may vary.
>


I think I covered that in "I can think of a bunch of reasons why it's a good
idea.. " - but the current implementation is hardcoded in the kernel so
there is no problem with *certain* boards having it done this way, and that
information being moved from the kernel into a static entry in a device
tree.

-- 
Matt Sealey <matt@genesi-usa.com>
Genesi, Manager, Developer Relations

[-- Attachment #2: Type: text/html, Size: 1455 bytes --]