From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] can I build two copies of uboot in buildroot?
Date: Sat, 26 Jan 2013 10:45:08 +0100 [thread overview]
Message-ID: <87wqv0ffbv.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1359148418.7974.65.camel@genx> (John Stile's message of "Fri, 25 Jan 2013 13:13:38 -0800")
>>>>> "John" == John Stile <john@stilen.com> writes:
John> I have hacked at91bootstrap to select and boot one of two copies of
John> uboot+env on a NAND flash, but I had to compile the second uboot my
John> self, since the environment address is set at compile time, and
John> buildroot only builds one copy of uboot.
Yes, you can (currently) only build a single u-boot in buildroot.
John> How might I hack uboot to build two different copies of uboot? I'm just
John> changing the address location of the uboot environment, and saving the
John> image as a different name.
Why not just use redundant u-boot environment and let both u-boots use
both? That way both environments are in sync and you gain redundancy.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-01-26 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 21:13 [Buildroot] can I build two copies of uboot in buildroot? John Stile
2013-01-26 0:01 ` John Stile
2013-01-26 9:45 ` Peter Korsgaard [this message]
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=87wqv0ffbv.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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