From: Boaz Ben-David <boaz.bd@wellsense-tech.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: bareboxenv usage
Date: Tue, 13 Sep 2011 15:07:16 +0300 [thread overview]
Message-ID: <4E6F4774.5010800@wellsense-tech.com> (raw)
In-Reply-To: <4E6F4604.7040501@pengutronix.de>
On 09/13/11 15:01, Marc Kleine-Budde wrote:
> On 09/13/2011 11:48 AM, Boaz Ben-David wrote:
>> On 09/13/11 12:14, Marc Kleine-Budde wrote:
>>> 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
>>>
>> Hi,
>>
>>
>> Thanks for the reply.
>>
>> First question, please tell me if these sequences are correct:
> basically yes....but
>
>> In Linux:
>>
>> - Read:
>>
>> 1.nanddump from the mtd device to a file.
> read the nanddump help text, you need to skip bad blocks
>
>> 2.bareboxenv -l the file dumped.
>>
>> -Write:
>>
>> 1.bareboxenv -s from source directory to a file
>>
>> 2.nandwrite that file to the mtd device.
> use padding
>
> cheers, Marc
>
Hi,
This was psuedo command line (:
Of course I will use padding and skip bb...
Thanks,
Boaz.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-09-13 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-12 13:54 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
2011-09-13 12:01 ` Marc Kleine-Budde
2011-09-13 12:07 ` Boaz Ben-David [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=4E6F4774.5010800@wellsense-tech.com \
--to=boaz.bd@wellsense-tech.com \
--cc=barebox@lists.infradead.org \
--cc=mkl@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox