Paul Fertser wrote: > In this case, yes. With Qi in NAND that's not so, as far as i > understand. Nevertheless, what will be if one block wears out in the > kernel partition? The user won't be able to even mount his NAND rootfs > after the next boot to save configuration/data and that is probably > important for many users.
You mean that the work-out block would change the offset calculation ? That won't happen, because the work-out block gets marked only in the BBT and Qi does't look there. (See my previous mail on the topic.) > That is, to be absolutely sure that the flashing will be done to the > correct addresses, everytime before dfu-ing anything a user must issue > a dynpart command in NOR u-boot? Naw, NOR u-boot takes care of that for you. See the script starting at line 87 of http://svn.openmoko.org/trunk/src/host/devirginator/mknor > Basically, people tried to "nandwrite -pm /dev/mtd3 uImage-GTA02.bin" > and nandwrite marked plenty of blocks bad. Hmm, did they flash_eraseall /dev/mtd3 first ? If not, nandwrite will understandably get rather confused and the -m makes sure this far from the end of your worries ... Actually, where do these flash instructions come from ? I thought we used to have them right ... - Werner
