From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] actual stxxtc board maintainer?
Date: Mon, 26 Nov 2007 23:25:06 +0100 [thread overview]
Message-ID: <20071126222506.726D2248DB@gemini.denx.de> (raw)
In-Reply-To: Your message of "Mon, 26 Nov 2007 13:47:30 EST." <474B14C2.8030708@ge.com>
In message <474B14C2.8030708@ge.com> you wrote:
>
> Passing bd_t via the device tree is evil and should die (it probably is
Agreed.
> Passing the u-boot env via the device tree seems like a very useful
> thing to keep. IMHO, this is a better way of accessing the u-boot
Ummm ... what would itr be good for?
> variables than fw_printenv. The problem with this concept currently is that
In which way is that better? One significan drawback is that such
access would necessarily be read-only, while with fw_setenv you can
modify the environment.
But really, why would an additional copy be better? TO me it seems
just a waste of CPU cycles and memory footprint.
> I would propose we keep the ability to embed the env variables in the
> blob, positioning ourselves to improving (a) and (b) going forward.
I fail to see any benefit from doing that...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Everything should be made as simple as possible, but not simpler."
- Albert Einstein
next prev parent reply other threads:[~2007-11-26 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 16:58 [U-Boot-Users] actual stxxtc board maintainer? Kumar Gala
2007-11-26 18:00 ` Dan Malek
2007-11-26 18:23 ` Kumar Gala
2007-11-26 18:47 ` Jerry Van Baren
2007-11-26 22:25 ` Wolfgang Denk [this message]
2007-11-27 12:50 ` [U-Boot-Users] LIBFDT: bd_t and env embedding (was actual stxxtc board maintainer?) Jerry Van Baren
2007-11-27 22:02 ` Wolfgang Denk
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=20071126222506.726D2248DB@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.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