From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] designing a firmware update mechanism
Date: Fri, 18 Jan 2013 12:30:28 +0100 [thread overview]
Message-ID: <1366890.AleMb1sNgO@sagittae> (raw)
In-Reply-To: <1358460573.32266.63.camel@genx>
On Thursday 17 January 2013 14:09:33 John Stile wrote:
[...]
> So far I am trying to split NAND in redundant halves (each with a copy
> of uboot + uboot-env + kernel + roofs), and modify at91bootstrap to
> choose which uboot to load, based on something inside the uboot-env
> areas.
>
> Will I need to compile 2 versions of uboot, differing only in where to
> look for the uboot-env, or is there another way?
Two different version of firmware does not looks a good idea. at91bootstrap
knows which copy of uboot is started/I suggest to find a way to pass this
information to uboot. With this information, uboot know which uboot-env to
use.
[...]
--
J?r?me Pouiller
next prev parent reply other threads:[~2013-01-18 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 22:09 [Buildroot] designing a firmware update mechanism John Stile
2013-01-18 11:30 ` Jérôme Pouiller [this message]
2013-01-18 13:55 ` Peter Korsgaard
2013-01-20 10:48 ` Arnout Vandecappelle
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=1366890.AleMb1sNgO@sagittae \
--to=jezz@sysmic.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