Hi Scott,
On Dec 11, 2012, at 12:53 AM, Scott Wood wrote:
On 12/10/2012 09:24:24 AM, Pantelis Antoniou wrote:
When accessing nand any bad blocks encountered are skipped, with no
indication about the amount of bad blocks encountered.
While this is normally fine, when you have to write a large
On 12/11/2012 03:40:53 AM, Pantelis Antoniou wrote:
Hi Scott,
On Dec 11, 2012, at 12:53 AM, Scott Wood wrote:
+/**
+ * nand_extent_skip_bad:
+ *
+ * Find the extent of a chunk, return the offset where it ends
+ * Blocks that are marked bad are skipped and the next block is
examined
+ *
Hi Scott,
On Dec 11, 2012, at 7:13 PM, Scott Wood wrote:
On 12/11/2012 03:40:53 AM, Pantelis Antoniou wrote:
Hi Scott,
On Dec 11, 2012, at 12:53 AM, Scott Wood wrote:
+/**
+ * nand_extent_skip_bad:
+ *
+ * Find the extent of a chunk, return the offset where it ends
+ * Blocks that
When accessing nand any bad blocks encountered are skipped, with no
indication about the amount of bad blocks encountered.
While this is normally fine, when you have to write a large amount
of data in chunks, you need to account for the skipped amount due
to the presence of the bad blocks.
On 12/10/2012 09:24:24 AM, Pantelis Antoniou wrote:
When accessing nand any bad blocks encountered are skipped, with no
indication about the amount of bad blocks encountered.
While this is normally fine, when you have to write a large amount
of data in chunks, you need to account for the skipped
5 matches
Mail list logo
