linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Meriin Michael-BMM063 <Meriin@motorola.com>,
	"'Ricardo DIz'" <rdiz@alumni.deec.uc.pt>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: U-Boot and kernel 2.6
Date: Fri, 11 Jun 2004 16:09:14 +0200	[thread overview]
Message-ID: <20040611140919.84651C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 11 Jun 2004 16:23:21 +0300." <40C9B249.4070905@intracom.gr>


Dear Pantelis,

in message <40C9B249.4070905@intracom.gr> you wrote:
>
> >No, this is IMHO not a good idea. Some of the information that  needs
> >to  be  passed to the kernel is not contained in the envrionment, and
> >does not belong there.
> >
> I'm just talking about augmenting the information provided by bd_t.

Again, no. It makes no sense to implement two  (or  more)  interfaces
for  the  same  purpose.  Let's  do it once, and right. It has become
clear that the bd_t stuff is not flexible enough, so let's get rid of
it and replace it, instead of adding more crap^H^H^H^H stuff  on  top
of it.

> And it's not just things that the kernel needs, it can be used to
> pass information to the user-space applications.

But this is nothing now. You have always been able to read and  write
the  U-Boot  environment  from applications. But this is a completely
unrelated topic.

Similarly it's trivial to parse /proc/cmdline by a script or  program
to  extract any information you might be looking for. But again, this
has nothing to do with  the  way  how  the  boot  loader  passes  the
required information to the kernel.

> Reading the environment from flash is not correct because the
> variables might be modified by the boot sequence but not commited.

This depends  on  what  you  are  doing.  Of  course  it  is  in  the
responsibility  of  the user to define which data to use, and when or
where to place a "setenv" in the boot script (if really needed). "Not
correct" is just your opinion for a very specuific mode  of  usage  -
which  just  indicates the problem: the U-Boot environment is NOT the
right place to look for the information you are after.

> When I get some breathing time, I'll sent you the patch.

Be prepared that I might ignore it.

Best regards,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
It all seemed, he thought, to be rather a lot of  trouble  to  go  to
just sharpen a razor blade.  - Terry Pratchett, _The Light Fantastic_

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-06-11 14:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10  6:45 U-Boot and kernel 2.6 Meriin Michael-BMM063
2004-06-11 10:36 ` David Woodhouse
2004-06-11 11:03   ` Pantelis Antoniou
2004-06-11 11:20     ` David Woodhouse
2004-06-11 13:03     ` Wolfgang Denk
2004-06-11 13:23       ` Pantelis Antoniou
2004-06-11 14:09         ` Wolfgang Denk [this message]
     [not found]           ` <40C9BED6.3010809@intracom.gr>
2004-06-11 14:34             ` David Woodhouse
2004-06-11 15:11               ` Wolfgang Denk
2004-06-11 17:17                 ` Greg Goodwin
2004-06-11 15:31               ` Mark Chambers
2004-06-11 16:22                 ` Wolfgang Denk
2004-06-11 16:48                 ` Kenneth Johansson
2004-06-11 14:43             ` Wolfgang Denk
2004-06-11 21:35               ` Mark A. Greer
2004-06-11 23:18                 ` Mark Chambers
2004-06-11 23:27                   ` Mark A. Greer
2004-06-12  2:12                 ` Kumar Gala
2004-06-11 16:48             ` Tom Rini
     [not found] ` <0F48024310E5D6118D200002B3A440DB08B07A3D@zil01exm08.mcil.comm.mot.com >
2004-06-11 19:27   ` Ricardo DIz
  -- strict thread matches above, loose matches on Subject: below --
2004-06-09 17:47 Ricardo DIz
2006-08-01  5:12 ` Dmitry Chichkov
2006-08-01  7:10   ` 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=20040611140919.84651C109F@atlas.denx.de \
    --to=wd@denx.de \
    --cc=Meriin@motorola.com \
    --cc=dwmw2@infradead.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=panto@intracom.gr \
    --cc=rdiz@alumni.deec.uc.pt \
    /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).