All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
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:01:02 -0600	[thread overview]
Message-ID: <45F6F4EE.8090504@freescale.com> (raw)
In-Reply-To: <F7652F68-D6FF-465C-BC8F-4F0C4D976AC0@kernel.crashing.org>

Kumar Gala wrote:
> On Mar 13, 2007, at 1:16 PM, Scott Wood wrote:
>> On Mon, Mar 12, 2007 at 04:07:57PM -0500, Kumar Gala wrote:
>>> 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.

How?  Any means I can think of would be uglier, more complex, and/or put 
information in the bootwrapper that it shouldn't have.

I think it belongs in the dts, anyway...  The default serial port is 
more a property of the board than a configuration issue (although it has 
aspects of both).  Any bootloader that wants to set a non-default serial 
port is welcome to overwrite the property.

-Scott

  reply	other threads:[~2007-03-13 22:59 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
2007-03-13 19:01       ` Scott Wood [this message]
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=45F6F4EE.8090504@freescale.com \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.