From: Anders Larsen <al@alarsen.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Wrong location of environment. Copy environment, substitute variables?
Date: Fri, 07 Jul 2006 16:13:32 +0200 [thread overview]
Message-ID: <pan.2006.07.07.14.13.32.809057@alarsen.net> (raw)
In-Reply-To: 1152280943.19463.49.camel@localhost.localdomain
On Fri, 07 Jul 2006 17:02:23 +0300, Andrew Zhukov wrote:
> I have at91rm9200dk with SPI DataFlash only (without Flash), u-boot
> 1.1.4, kernel 2.6.10.
>
> I'd like the kernel to use u-boot's "bootargs" as cmdline. To use
> u-boot's data the kernel should know its absolute locations...
> I see the kernel expects environment at TEXT_BASE + 0x100 (that's
> 20000100), but u-boot places environment at 21ede00c (result of function
> env_get_addr(0)). I believe the last will move if I edit smth in u-boot.
>
> Summary: in function do_bootm (where u-boot starts loading the kernel),
> I should copy the whole environment to the area starting from location
> 20000100.
>
> Is this right way?
No no no!
The kernel expects a tagged list of parameters at 0x20000100; this list
includes - among other values - the contents of "bootargs" tagged as
command-line "ATAG_CMDLINE" (only the contents of bootargs is copied;
other u-boot environment variables are not).
This already works out-of-the-box.
> Trouble: bootm doesn't substitute variables (${ipaddr} ${serverip}
> etc.). I should copy-substitute. There should be a function for
> substitution - does anybody know?
With the hush parser you can use a trick like e.g.
setenv bootcmd setenv bootargs ip=${ipaddr} ... \; bootm 0x10040000
'boot' will then set the bootargs variable just prior to booting.
Cheers
Anders
next prev parent reply other threads:[~2006-07-07 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 14:02 [U-Boot-Users] Wrong location of environment. Copy environment, substitute variables? Andrew Zhukov
2006-07-07 14:13 ` Anders Larsen [this message]
2006-07-08 10:40 ` 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=pan.2006.07.07.14.13.32.809057@alarsen.net \
--to=al@alarsen.net \
--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 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.