From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kyungmin Park <kmpark@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] OneNAND: Runtime badblock check support
Date: Wed, 22 Jul 2009 09:19:50 +0300 [thread overview]
Message-ID: <1248243590.24676.17.camel@localhost> (raw)
In-Reply-To: <9c9fda240907211939ud11b9adiae68c076bfbbe36f@mail.gmail.com>
On Wed, 2009-07-22 at 11:39 +0900, Kyungmin Park wrote:
> Hi,
>
> On Tue, Jul 21, 2009 at 8:05 PM, Kyungmin Park<kmpark@infradead.org> wrote:
> > Hi
> >
> > On Tue, Jul 21, 2009 at 7:56 PM, Artem Bityutskiy<dedekind1@gmail.com> wrote:
> >> Hi,
> >>
> >> On 07/21/2009 05:53 AM, Kyungmin Park wrote:
> >>>
> >>> At bootloader, we don't need to read full page. It takes too long time.
> >>> Instead it only read pages required for boot.
> >>>
> >>> Signed-off-by: Kyungmin Park<kyungmin.park@samsung.com>
> >>> ---
> >>
> >> I do not understand the commit message. Could you please provide a better
> >> one which explains what the patch is really doing and why.
> >
> > Right, the page means all blocks. It doesn't scan all blocks at boot
> > time. only some block contains kernel part are read and boot.
> >
> > The goal is simple, Avoid double scanning at boot time. One time for
> > bootloader, Another is kernel.
> > As you know at bootloader, only load kernel in normal case. it means
> > we only read the kernel bad blocks and handle it.
> > and jump to the kernel. that's all
> >
I understand the double-scanning issue. But I still do not understand
how your patch is avoiding it? If the boot-loader has scanned the
flash, it should pass the bad-block bitmap to the kernel. If you have
on-flash BBT, then probably this is not a problem.
> Experimental idea.
> How about to integrate the bbt scan and ubi scan?
It is possible, but isn't it better to just have on-flash BBT and
forget about any scanning for bad blocks at all?
We could go even further: If the boot-loader supports ubi, it could do
the scanning and pass all UBI data to the kernel, in which case UBI
would not need to do any scanning.
> At ubi scan time. it scans all ubi blocks. In different from NAND,
> OneNAND read main page and spare page both.
> So if runtime badblock check enabled, read the page and check oob
> first and if it's valid. use main page. If not, set it's badblock.
> I'm not sure how much codes are modified. :)
>
> How to you think?
It is possible, but I think the implementation will add more ugliness...
Why not to just use on-flash BBT instead?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-07-22 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 2:53 [PATCH] OneNAND: Runtime badblock check support Kyungmin Park
2009-07-21 10:56 ` Artem Bityutskiy
2009-07-21 11:05 ` Kyungmin Park
2009-07-22 2:39 ` Kyungmin Park
2009-07-22 6:19 ` Artem Bityutskiy [this message]
2009-07-22 7:11 ` Kyungmin Park
2009-07-22 7:28 ` Artem Bityutskiy
2009-07-22 7:59 ` Kyungmin Park
2009-07-22 8:12 ` Amit Kumar Sharma
2009-07-22 8:26 ` Artem Bityutskiy
2009-07-24 15:31 ` Artem Bityutskiy
2009-07-24 23:17 ` Kyungmin Park
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=1248243590.24676.17.camel@localhost \
--to=dedekind1@gmail.com \
--cc=kmpark@infradead.org \
--cc=linux-mtd@lists.infradead.org \
/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