From mboxrd@z Thu Jan 1 00:00:00 1970 From: ran shalit Date: Fri, 18 Mar 2011 11:54:43 -0700 (PDT) Subject: [U-Boot] Q: nand usage In-Reply-To: <20110318184250.71829EA440@gemini.denx.de> References: <20110318163541.B9E99B36F@gemini.denx.de> <31183736.post@talk.nabble.com> <20110318184250.71829EA440@gemini.denx.de> Message-ID: <31184035.post@talk.nabble.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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. Thanks again, Ran -- View this message in context: http://old.nabble.com/-U-Boot--Q%3A-nand-usage-tp31178552p31184035.html Sent from the Uboot - Users mailing list archive at Nabble.com.