From: Geiger Ho <geiger.ho@fmp.fujitsu.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] onenand bad block handling
Date: Wed, 13 May 2009 18:10:12 +0800 [thread overview]
Message-ID: <4A0A9C84.7010601@fmp.fujitsu.com> (raw)
In-Reply-To: <EB74B55668EC45AF8635DC58133D3BD0@sisodomain.com>
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
>>
>
>
>
>
prev parent reply other threads:[~2009-05-13 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A0A9C84.7010601@fmp.fujitsu.com \
--to=geiger.ho@fmp.fujitsu.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox