All of lore.kernel.org
 help / color / mirror / Atom feed
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 11:14:57 +0200	[thread overview]
Message-ID: <4E6F1F11.6070206@pengutronix.de> (raw)
In-Reply-To: <4E6F1B57.7060507@wellsense-tech.com>


[-- Attachment #1.1: Type: text/plain, Size: 674 bytes --]

On 09/13/2011 10:59 AM, Boaz Ben-David wrote:
> All I am asking is: do I need to use /dev/mtdblock or /dev/mtd when
> loading and saving envs

neither nor - loadenv & saveenv are not bad block aware. In barebox you
use the .bb devices, which are bad block are, under linux use nandwrite
+ nanddump to write or read data from the nand into a file. Then use
loadenv/saveenv.

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

  reply	other threads:[~2011-09-13  9:15 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 [this message]
2011-09-13  9:48     ` Boaz Ben-David
2011-09-13 11:25       ` Boaz Ben-David
2011-09-13 12:00         ` Marc Kleine-Budde
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=4E6F1F11.6070206@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.