From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Woodhouse, David" <david.woodhouse@intel.com>
Cc: Dan Carpenter <error27@gmail.com>, Barry Song <21cnbao@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Dominik Brodowski <linux@dominikbrodowski.net>,
"Hunter, Adrian" <adrian.hunter@intel.com>,
Gabor Juhos <juhosg@openwrt.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Jonas Gorski <jonas.gorski@gmail.com>,
Jamie Iles <jamie@jamieiles.com>,
Ivan Djelic <ivan.djelic@parrot.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Maxim Levitsky <maximlevitsky@gmail.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
Kevin Cernekee <cernekee@gmail.com>,
Kulikov Vasiliy <segooon@gmail.com>,
Jim Quinlan <jim2101024@gmail.com>,
Andres Salomon <dilinger@queued.net>,
Axel Lin <axel.lin@gmail.com>, Anatolij Gustschin <agust@denx.de>,
Mike Frysinger <vapier@gentoo.org>, Arnd Bergmann <arnd@arndb.de>,
Lei Wen <leiwen@marvell.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Florian Fainelli <florian@openwrt.org>,
Peter Wippich <pewi@gw-instruments.de>,
Matthieu CASTET <matthieu.castet@parrot.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Shmulik Ladkani <shmulik.ladkani@gmail.com>,
Wolfram Sang <w.sang@pengutronix.de>,
"Dong, Chuanxiao" <chuanxiao.dong@intel.com>,
Joe Perches <joe@perches.com>,
Guillaume LECERF <glecerf@gmail.com>,
Brian Norris <computersforpeace@gmail.com>,
Roman Tereshonkov <roman.tereshonkov@nokia.com>
Subject: Re: [PATCH v3 0/6] NAND BBM + BBT updates
Date: Tue, 17 Jan 2012 10:27:42 +0200 [thread overview]
Message-ID: <1326788862.28708.2.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1326788619.28708.0.camel@sauron.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 683 bytes --]
[Sorry, did not finish the e-mail :-)]
On Tue, 2012-01-17 at 10:23 +0200, Artem Bityutskiy wrote:
> Well, I am 100% not sure of course. But think that because marking blocks as bad using OOB is
> the standard way, and vendors know about this, and they know that flash
> bad blocks become bad, they will probably make try to make this
> mechanism work for the users. But even if this is not true for a
> specific chip, then the users should have BBT, and it will be used. But
> I do not believe that
that current MTD BBT is reliable enough for modern flashes. For such
a hypothetical chip ti would have to be carefully assessed.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-01-17 8:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 20:23 [PATCH v3 0/6] NAND BBM + BBT updates Brian Norris
2012-01-09 20:23 ` [PATCH v3 1/6] mtd: nand: add NAND_NO_WRITE_OOB option Brian Norris
2012-01-09 20:23 ` [PATCH v3 2/6] mtd: nand: write bad block marker by default even with BBT Brian Norris
2012-01-09 20:23 ` [PATCH v3 3/6] mtd: nand: erase block before marking bad Brian Norris
2012-01-13 22:42 ` Artem Bityutskiy
2012-01-13 23:07 ` Brian Norris
2012-01-09 20:23 ` [PATCH v3 4/6] mtd: nand: fix SCAN2NDPAGE check for BBM Brian Norris
2012-01-09 20:23 ` [PATCH v3 5/6] mtd: nand: differentiate 1- vs. 2-byte writes when marking bad blocks Brian Norris
2012-01-09 20:23 ` [PATCH v3 6/6] mtd: nand: correct comment on nand_chip badblockbits Brian Norris
2012-01-10 9:44 ` [PATCH v3 0/6] NAND BBM + BBT updates Sebastian Andrzej Siewior
2012-01-10 18:54 ` Brian Norris
2012-01-11 22:28 ` Artem Bityutskiy
2012-01-12 7:58 ` Shmulik Ladkani
2012-01-13 22:12 ` Artem Bityutskiy
2012-01-16 19:35 ` Shmulik Ladkani
2012-01-12 9:09 ` Sebastian Andrzej Siewior
2012-01-13 22:36 ` Artem Bityutskiy
2012-01-16 20:59 ` Woodhouse, David
2012-01-17 8:23 ` Artem Bityutskiy
2012-01-17 8:27 ` Artem Bityutskiy [this message]
2012-01-17 11:19 ` Angus CLARK
2012-01-17 13:06 ` Ivan Djelic
2012-01-18 22:18 ` Brian Norris
2012-01-17 10:22 ` Angus CLARK
2012-01-17 13:33 ` Artem Bityutskiy
2012-01-18 22:04 ` Brian Norris
2012-01-19 9:30 ` Angus CLARK
2012-01-19 9:59 ` Ricard Wanderlof
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=1326788862.28708.2.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=21cnbao@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=agust@denx.de \
--cc=arnd@arndb.de \
--cc=axel.lin@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=cernekee@gmail.com \
--cc=chuanxiao.dong@intel.com \
--cc=computersforpeace@gmail.com \
--cc=david.woodhouse@intel.com \
--cc=dbaryshkov@gmail.com \
--cc=dilinger@queued.net \
--cc=error27@gmail.com \
--cc=florian@openwrt.org \
--cc=glecerf@gmail.com \
--cc=ivan.djelic@parrot.com \
--cc=jamie@jamieiles.com \
--cc=jim2101024@gmail.com \
--cc=joe@perches.com \
--cc=jonas.gorski@gmail.com \
--cc=juhosg@openwrt.org \
--cc=kyungmin.park@samsung.com \
--cc=leiwen@marvell.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
--cc=matthieu.castet@parrot.com \
--cc=maximlevitsky@gmail.com \
--cc=nicolas.ferre@atmel.com \
--cc=pewi@gw-instruments.de \
--cc=robert.jarzmik@free.fr \
--cc=roman.tereshonkov@nokia.com \
--cc=s.hauer@pengutronix.de \
--cc=segooon@gmail.com \
--cc=shmulik.ladkani@gmail.com \
--cc=vapier@gentoo.org \
--cc=w.sang@pengutronix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.