bareboxenv usage

[Boaz Ben-David]

On 09/13/11 12:48, 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:
>
> In Linux:
>
> - Read:
>
> 1.nanddump from the mtd device to a file.
>
> 2.bareboxenv -l the file dumped.
>
> -Write:
>
> 1.bareboxenv -s from source directory to a file
>
> 2.nandwrite that file to the mtd device.
>
>
> Second question is: what would be the same sequences under barebox?
>
>
> Thanks,
>
>
> Boaz.
>
>
> _______________________________________________
> barebox mailing list
> barebox at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox

There's something I don't get.

If loadenv/saveenv are not bad-block aware, why are they used 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?


Thanks,

Boaz.