<br><br><div class="gmail_quote">On Tue, Nov 25, 2008 at 3:05 PM, Wolfgang Denk <span dir="ltr"><<a href="mailto:wd@denx.de">wd@denx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Dear Matt,<br>
<div class="Ih2E3d"><br>
In message <<a href="mailto:b5e2fc790811251131g63ea9444x57ec0829ca0b069e@mail.gmail.com">b5e2fc790811251131g63ea9444x57ec0829ca0b069e@mail.gmail.com</a>> you wrote:<br>
><br>
> There is also no reason you can't hard-code the locations into the device<br>
> tree, to support older U-Boots that don't know about<br>
> /chosen/linux,log-metadata and /chosen/linux,log-buffer*.<br>
<br>
</div>Actually there is such reason - U-Boot traditionally allocates the log<br>
buffer close to the upper end of system memory, so the start address<br>
depends on the memory size on the board, which may vary.<br>
</blockquote><div><br><br>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.<br>
</div></div>-- <br>Matt Sealey <<a href="mailto:matt@genesi-usa.com">matt@genesi-usa.com</a>><br>Genesi, Manager, Developer Relations<br>