From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Boaz Ben-David <boaz.bd@wellsense-tech.com>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: bareboxenv usage
Date: Tue, 13 Sep 2011 14:00:03 +0200 [thread overview]
Message-ID: <4E6F45C3.6040803@pengutronix.de> (raw)
In-Reply-To: <4E6F3DA8.40904@wellsense-tech.com>
[-- Attachment #1.1: Type: text/plain, Size: 910 bytes --]
On 09/13/2011 01:25 PM, Boaz Ben-David wrote:
> There's something I don't get.
>
> If loadenv/saveenv are not bad-block aware, why are they used in barebox
> by default?
They operate on bad block aware devices (in barebox) by default.
> When the system boots envfs_load is used to load the environment from
> /dev/env0 or whatever.
>
> If /dev/env0 is not bad-block aware device (like the bb devices) this
> means this could fail because of
> a bad block in the env partition. Am I right?
Nope - the raw NAND is usually attached as "/dev/env0_raw" and the bad
block aware device as "/dev/env0".
cheers, Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-09-13 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 13:54 bareboxenv usage Boaz Ben-David
2011-09-13 8:59 ` Boaz Ben-David
2011-09-13 9:14 ` Marc Kleine-Budde
2011-09-13 9:48 ` Boaz Ben-David
2011-09-13 11:25 ` Boaz Ben-David
2011-09-13 12:00 ` Marc Kleine-Budde [this message]
2011-09-13 12:01 ` Marc Kleine-Budde
2011-09-13 12:07 ` Boaz Ben-David
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=4E6F45C3.6040803@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=boaz.bd@wellsense-tech.com \
/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.