From: George G. Davis <gdavis@mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] bootargs
Date: Thu, 14 Oct 2004 16:07:34 -0400 [thread overview]
Message-ID: <20041014200734.GM8731@mvista.com> (raw)
In-Reply-To: <45ABD2373C33C4459D42B40EC4F346F203AE7959@FTWMLVEM03.e2k.ad.ge.com>
On Thu, Oct 14, 2004 at 10:20:29AM -0500, Barbier, Renaud (GE Infrastructure) wrote:
> I am not sure that I understand how to pick up the bootargs variables in Linux (ocotea) PPC.
Sorry, my comments earlier in this thread were relevant for ARM targets only.
I have no idea how this works for PPC or other archs.
--
Regards,
George
> I looked at codes of different machine but I do not know which one fit fro my 440GX based-machine.
>
> I am still looking into these bd_t and bi_record structure to see if I can find the answer.
>
> Any help welcome?
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users
next prev parent reply other threads:[~2004-10-14 20:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 15:20 [U-Boot-Users] bootargs Barbier, Renaud
2004-10-14 20:07 ` George G. Davis [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-14 20:17 Barbier, Renaud
2004-03-26 12:39 asnua at eircom.net
2004-03-26 13:30 ` Wolfgang Denk
2004-03-11 13:13 asnua at eircom.net
2004-03-11 13:36 ` Wolfgang Denk
2004-03-10 18:33 asnua at eircom.net
2004-03-10 19:30 ` George G. Davis
2004-03-10 20:21 ` 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=20041014200734.GM8731@mvista.com \
--to=gdavis@mvista.com \
--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