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.
>
> 1. How does the u-boot handle bad block for onenand?
Jsut skip the bad block and use only good bloks
> 2. 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.
> 3. 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
> [email protected]
> http://lists.denx.de/mailman/listinfo/u-boot
_______________________________________________
U-Boot mailing list
[email protected]
http://lists.denx.de/mailman/listinfo/u-boot
