On Monday, September 12, 2011 09:19:06 PM Scott Wood wrote:
On 09/12/2011 01:36 PM, Marek Vasut wrote:
On Monday, September 12, 2011 08:31:12 PM Scott Wood wrote:
Would it make sense to have the driver code treat block 0 specially (possibly conditioned on an hwconfig or compile-time config), rather than have it be user-driven?
No! What if (very possible situation actually) the user wants to use the whole NAND because the user is booting from SD/SPI/... ?
Well, that's why I suggested it be configurable.
I'm curious why anything is written on an erase, though, regardless of data format.
Badblock markers (some FSL invention) are written always.
What's it doing with them? Migrating them is something that should only happen on the first use, as there will later be data in the factory bad block area, right? So it shouldn't be "always". Migration should be an explicitly requested option. Like scrub. :-)
Where is the code that does this? Which driver?
The BCH accelerator does this.
-Scott