From: "Bityutskiy, Artem" <artem.bityutskiy@intel.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: Huang Shijie <b32955@freescale.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>
Subject: Re: [PATCH v3] mtd/gpmi : add BBT support to gpmi nand driver
Date: Thu, 2 Feb 2012 11:51:25 +0000 [thread overview]
Message-ID: <1328183611.28171.170.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20120131121007.GO2471@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 1010 bytes --]
On Tue, 2012-01-31 at 13:10 +0100, Wolfram Sang wrote:
> On Tue, Jan 31, 2012 at 07:11:56PM +0800, Huang Shijie wrote:
> > Add a new field to gpmi_nand_platform_data{}.
> > Make the BBT support to board specific.
> >
> > Signed-off-by: Huang Shijie <b32955@freescale.com>
>
> Reviewed-by: Wolfram Sang <w.sang@pengutronix.de>
>
> I'd think you won't be able to mark blocks bad, though. Will send a
> patch in a minute. Please test.
Sorry, I have not read this and the previous related long threads, but
from the few first e-mails I got the impression that you are not aware
of the patch from Brian Norris where he modifies MTD BBT code so that it
will by default write bad block markers _both_ to the BBT and to OOB. It
sounds like you should hold on with this patch and wait when Brian's
patch gets in. Then you probably may just use the first version of this
patch.
The patch I referred to:
http://patchwork.ozlabs.org/patch/137154/
HTH.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 464 bytes --]
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2012-02-02 11:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 11:11 [PATCH v3] mtd/gpmi : add BBT support to gpmi nand driver Huang Shijie
2012-01-31 11:34 ` Marek Vasut
2012-01-31 12:10 ` Wolfram Sang
2012-02-02 11:51 ` Bityutskiy, Artem [this message]
2012-02-02 13:29 ` Lothar Waßmann
2012-02-02 14:01 ` Ricard Wanderlof
2012-02-02 14:43 ` Lothar Waßmann
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=1328183611.28171.170.camel@sauron.fi.intel.com \
--to=artem.bityutskiy@intel.com \
--cc=b32955@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox