public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
* [U-Boot] onenand bad block handling
@ 2009-05-11 10:24 Geiger Ho
  2009-05-11 10:56 ` Amit Kumar Sharma
  0 siblings, 1 reply; 3+ messages in thread
From: Geiger Ho @ 2009-05-11 10:24 UTC (permalink / raw)
  To: u-boot

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?
  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?
  3. How to deal with bad blocks after the writing of the u-boot, kernel 
and rootfs image? Is it the job of UBI?

  Thanks in advance.

Best regards,
Geiger

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-05-13 10:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-11 10:24 [U-Boot] onenand bad block handling Geiger Ho
2009-05-11 10:56 ` Amit Kumar Sharma
2009-05-13 10:10   ` Geiger Ho

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox