From mboxrd@z Thu Jan 1 00:00:00 1970 From: Geiger Ho Date: Wed, 13 May 2009 18:10:12 +0800 Subject: [U-Boot] onenand bad block handling In-Reply-To: References: <4A07FCC5.60905@fmp.fujitsu.com> Message-ID: <4A0A9C84.7010601@fmp.fujitsu.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi Sharma-san, If I use u-boot to write kernel image to onenand that the kernel image across bad blocks, will u-boot able to skip blocks during read and successfully boot up the kernel? Also, same case for rootfs, if I write JFFS2 format rootfs to onenand using u-boot, how does the kernel handle the rootfs if rootfs across bad blocks? Many thanks. Best regards, Geiger Amit Kumar Sharma wrote: > 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 >> U-Boot at lists.denx.de >> http://lists.denx.de/mailman/listinfo/u-boot >> > > > >