11 May
2009
11 May
'09
12:56 p.m.
Hi,
Hi all,
I am working on an ARM platform with OneNAND as the permanent storage for u-boot, Linux kernel and rootfs. I am using u-boot-2009.03 and linux kernel 2.6.27. I have some questions about the bad block handling of OneNAND.
- How does the u-boot handle bad block for onenand?
Jsut skip the bad block and use only good bloks
- If u-boot is creating a bad block table, does it need
to pass to the kernel? If not, how to ensure their bad block table are in sync?
no need to pass bad block from uboot, kernel will create table of bad blocks.
- How to deal with bad blocks after the writing of the
u-boot, kernel and rootfs image? Is it the job of UBI?
yes, UBI will manage
Thanks in advance.
Best regards, Geiger _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot