Re: [PATCH v2 1/5] mtd: nand: Create a BBT flag to access bad block markers in raw mode

2015-07-24 Thread Andy Gross
On Tue, Jul 21, 2015 at 04:04:42PM +0530, Archit Taneja wrote: > Some controllers can access the factory bad block marker from OOB only > when they read it in raw mode. When ECC is enabled, these controllers > discard reading/writing bad block markers, preventing access to them > altogether. > >

Re: [PATCH v2 1/5] mtd: nand: Create a BBT flag to access bad block markers in raw mode

2015-07-24 Thread Andy Gross
On Tue, Jul 21, 2015 at 04:04:42PM +0530, Archit Taneja wrote: Some controllers can access the factory bad block marker from OOB only when they read it in raw mode. When ECC is enabled, these controllers discard reading/writing bad block markers, preventing access to them altogether. The

[PATCH v2 1/5] mtd: nand: Create a BBT flag to access bad block markers in raw mode

2015-07-21 Thread Archit Taneja
Some controllers can access the factory bad block marker from OOB only when they read it in raw mode. When ECC is enabled, these controllers discard reading/writing bad block markers, preventing access to them altogether. The bbt driver assumes MTD_OPS_PLACE_OOB when scanning for bad blocks. This

[PATCH v2 1/5] mtd: nand: Create a BBT flag to access bad block markers in raw mode

2015-07-21 Thread Archit Taneja
Some controllers can access the factory bad block marker from OOB only when they read it in raw mode. When ECC is enabled, these controllers discard reading/writing bad block markers, preventing access to them altogether. The bbt driver assumes MTD_OPS_PLACE_OOB when scanning for bad blocks. This