From: Artem Bityutskiy <dedekind@infradead.org>
To: Sudeep K N <sudeepholla.maillist@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI - Nand bad block management details required
Date: Fri, 22 Jun 2007 13:10:30 +0300 [thread overview]
Message-ID: <1182507030.4403.80.camel@sauron> (raw)
In-Reply-To: <366f00c80706220306l1e0ebcek3c7cdc988c82de81@mail.gmail.com>
On Fri, 2007-06-22 at 15:36 +0530, Sudeep K N wrote:
> Does the UBI depend on the bad block table(BBT) built by MTD?
Yes, it asks MTD if blocks are bad or not.
> In otherwords, can the complete chip scan during chip probe be avoided
> by enabling/setting NAND_SKIP_BBTSCAN in chip->options?
No, UBI relies on MTD in this. MTD supports on-flash BBT tables, so if
you do not want MTD level to do full chip scan you should use on-flash
BBT.
> Does UBI built BBT independent of the MTD built BBT?
No, it relies on MTD.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
prev parent reply other threads:[~2007-06-22 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 10:06 UBI - Nand bad block management details required Sudeep K N
2007-06-22 10:10 ` Artem Bityutskiy [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=1182507030.4403.80.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=sudeepholla.maillist@gmail.com \
/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