From: Kumar Gala <galak@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-dev@ozlabs.org,
U-Boot Users <u-boot-users@lists.sourceforge.net>
Subject: Re: FT u-boot shim
Date: Thu, 27 Apr 2006 14:54:54 -0500 [thread overview]
Message-ID: <9F5CC364-8FC8-48BA-8D12-E524815B6537@kernel.crashing.org> (raw)
In-Reply-To: <20060427194522.6FA1B353A57@atlas.denx.de>
On Apr 27, 2006, at 2:45 PM, Wolfgang Denk wrote:
> In message <2CD98C5D-
> E51C-49CA-9BDC-6FE4C1B67854@kernel.crashing.org> you wrote:
>>
>> We can do this w/o too much modification to what is happening in u-
>> boot today. I'd probably like to keep the ability to build a dev
>> tree into the u-boot binary, but make the preferred means to pass a
>
> I don't like this, as it's a very Linux-centric view, but U-Boot is
> supposed to be OS unaware and independent.
Hmm, I guess. There really isn't anything about the device tree that
is Linux specific. Other OSes could choice to use it. But lets
argue about that one once I've got the mechanism in which we pass the
blob in via the bootm command.
The only difference I see would be that the address of the blob would
be implicit if the blob was built into u-boot. We would still use a
passed in blob via the bootm command if given.
- kumar
next prev parent reply other threads:[~2006-04-27 19:54 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 19:30 FT u-boot shim Rune Torgersen
2006-04-27 19:40 ` Kumar Gala
2006-04-27 19:45 ` Wolfgang Denk
2006-04-27 19:54 ` Kumar Gala [this message]
2006-04-27 21:34 ` Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 21:43 85xx FDT updates? Kumar Gala
2006-04-25 18:14 ` Kumar Gala
2006-04-25 18:24 ` Eugene Surovegin
2006-04-25 18:29 ` Brent Cook
2006-04-25 18:33 ` Kumar Gala
2006-04-25 18:53 ` Eugene Surovegin
2006-04-25 20:00 ` FT u-boot shim Kumar Gala
2006-04-25 21:30 ` Wolfgang Denk
2006-04-25 21:33 ` Kumar Gala
2006-04-25 21:39 ` Wolfgang Denk
2006-04-25 21:42 ` Kumar Gala
2006-04-25 22:28 ` Wolfgang Denk
2006-04-26 14:37 ` Kumar Gala
2006-04-26 19:19 ` Wolfgang Denk
2006-04-26 19:46 ` Geert Uytterhoeven
2006-04-27 18:18 ` Kumar Gala
2006-04-27 19:05 ` Wolfgang Denk
2006-04-27 19:20 ` Kumar Gala
2006-04-27 19:33 ` Jerry Van Baren
2006-04-27 19:40 ` Wolfgang Denk
2006-04-27 19:46 ` Kumar Gala
2006-04-27 19:59 ` Kumar Gala
2006-04-27 21:36 ` Wolfgang Denk
2006-04-25 21:33 ` Mark A. Greer
2006-04-25 21:38 ` Eugene Surovegin
2006-04-28 11:28 ` Paul Mackerras
2006-04-28 16:01 ` Kumar Gala
2006-04-28 19:11 ` Wolfgang Denk
2006-04-28 19:44 ` Tom Rini
2006-04-28 23:07 ` Wolfgang Denk
2006-04-28 23:22 ` Tom Rini
2006-04-29 0:32 ` Wolfgang Denk
2006-04-29 0:52 ` Tom Rini
2006-04-29 8:37 ` Wolfgang Denk
2006-04-29 15:33 ` Kumar Gala
2006-04-28 23:35 ` Paul Mackerras
2006-04-28 23:55 ` Wolfgang Denk
2006-04-28 19:52 ` Tom Rini
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=9F5CC364-8FC8-48BA-8D12-E524815B6537@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=u-boot-users@lists.sourceforge.net \
--cc=wd@denx.de \
/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).