[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201403200933.39382.jbe@pengutronix.de>
Date: Thu, 20 Mar 2014 09:33:39 +0100
From: Juergen Beisert <jbe@...gutronix.de>
To: linux-arm-kernel@...ts.infradead.org
Cc: y@...o-electronics.de, Arnd Bergmann <arnd@...db.de>,
Artem Bityutskiy <artem.bityutskiy@...ux.intel.com>,
Brian Norris <computersforpeace@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
Fabio Estevam <fabio.estevam@...escale.com>,
Huang Shijie <b32955@...escale.com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Lothar Waßmann <LW@...o-electronics.de>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
Rob Herring <robh+dt@...nel.org>,
Rob Landley <rob@...dley.net>,
Russell King <linux@....linux.org.uk>,
Sascha Hauer <kernel@...gutronix.de>,
Shawn Guo <shawn.guo@...escale.com>,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-mtd@...ts.infradead.org
Subject: Re: [PATCH] mtd: gpmi: make blockmark swapping optional
Hi Lothar,
On Wednesday 19 March 2014 14:23:26 y@...o-electronics.de wrote:
> With a flash-based BBT there is no reason to move the Factory Bad
> Block Marker from the data area buffer (to where it is mapped by the
> GPMI NAND controller) to the OOB buffer. Thus, make this feature
> configurable via DT. This is required for the Ka-Ro electronics
> platforms.
> [...]
How do you create the BBT the very first time with valuable data when the NAND
already contains factory bad blocks?
jbe
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists