From: Kumar Gala <galak@kernel.crashing.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 17/19] bootwrapper: compatibility layer for old U-Boots (a.k.a. cuImage, cuboot)
Date: Tue, 13 Mar 2007 13:50:41 -0500 [thread overview]
Message-ID: <F7652F68-D6FF-465C-BC8F-4F0C4D976AC0@kernel.crashing.org> (raw)
In-Reply-To: <20070313181617.GA5360@ld0162-tx32.am.freescale.net>
On Mar 13, 2007, at 1:16 PM, Scott Wood wrote:
> On Mon, Mar 12, 2007 at 04:07:57PM -0500, Kumar Gala wrote:
>> On Mar 12, 2007, at 3:42 PM, Scott Wood wrote:
>>> The device trees currently in the kernel tree must have
>>> /chosen/linux,stdout-path added to work with cuboot.
>>
>> Why is linux,stdout-path needed by cuboot?
>
> It's used by serial.c to find the console, and the kernel requires
> it as
> well. There's no information in the bd_t that would allow the
> bootwrapper to generate this, so it has to come from the device tree.
>
> The only reason it's not required with dt-enabled u-boot is that u-
> boot
> has it hardcoded in the board's config file.
I don't think we should put this into the .dts but, have code in the
wrapper that handles it.
- k
next prev parent reply other threads:[~2007-03-13 23:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 20:42 [PATCH 17/19] bootwrapper: compatibility layer for old U-Boots (a.k.a. cuImage, cuboot) Scott Wood
2007-03-12 21:07 ` Kumar Gala
2007-03-13 18:16 ` Scott Wood
2007-03-13 18:50 ` Kumar Gala [this message]
2007-03-13 19:01 ` Scott Wood
2007-03-13 19:13 ` Kumar Gala
2007-03-13 19:25 ` Scott Wood
2007-03-12 21:12 ` Kumar Gala
2007-03-13 15:28 ` Scott Wood
2007-03-14 4:25 ` Paul Mackerras
2007-03-14 15:59 ` Scott Wood
2007-03-14 16:08 ` Kumar Gala
2007-03-14 16:45 ` Kim Phillips
2007-03-14 23:36 ` David Gibson
2007-03-15 15:17 ` Scott Wood
2007-03-14 6:35 ` David Gibson
2007-03-14 16:59 ` Scott Wood
2007-03-14 23:56 ` David Gibson
2007-03-15 16:40 ` Scott Wood
2007-03-16 0:09 ` David Gibson
2007-03-14 21:48 ` Mark A. Greer
2007-03-14 21:48 ` Scott Wood
2007-03-14 23:23 ` Mark A. Greer
2007-03-15 0:04 ` David Gibson
2007-03-15 1:59 ` Mark A. Greer
2007-03-15 2:02 ` David Gibson
2007-03-15 2:05 ` David Gibson
2007-03-15 2:15 ` Mark A. Greer
2007-03-15 2:12 ` Mark A. Greer
2007-03-29 23:12 ` Milton Miller
2007-03-15 0:01 ` David Gibson
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=F7652F68-D6FF-465C-BC8F-4F0C4D976AC0@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).