On Fri, 18 Mar 2011 11:54:43 -0700 ran shalit ranshalit@gmail.com wrote:
wd wrote:
I think my question was not very well expressed. I ment to ask about the mapping of the partitions inside the NAND: Does each partitions need some spare blocks (padding block) becuase of the bad block skipping in the Nand ? As I said, I did not find any information about the strategy of mapping partitions in the Nand.
As you are talking about partitions, I assume you refert to the MTD partitioning. In this case the bad block handling needs to be done in by the file system code, when you create a file system insinde one of the partitions.
[Note that this differs from UBI, where bad block handling is done for the whole device, independent of the volumes that you create on top of it.]
Sorry, I probably use the wrong terms in my question. I do not mean partition using file system, but just saving files using the u-boot interface, for example saving the kernel file in some space in the NAND and for the u-boot file in another space in the NAND, and all done with the given write command in the uboot (nand write...). And again with this u-boot interface I still need some strategy for deciding where to put each file.
Yes, when placing raw files in NAND, you want to leave some space for bad blocks.
-Scott