From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from scorch.co.nz ([203.167.210.162] helo=firstline.co.nz) by bombadil.infradead.org with smtp (Exim 4.69 #1 (Red Hat Linux)) id 1NHkcY-0001UM-S7 for linux-mtd@lists.infradead.org; Mon, 07 Dec 2009 20:55:55 +0000 From: Charles Manning To: linux-mtd@lists.infradead.org Subject: Re: What filesystem for NAND flash with OOB 218 Date: Tue, 8 Dec 2009 09:55:43 +1300 References: <4B1C682D.1020603@theptrgroup.com> <200912071619.56623.manningc2@actrix.gen.nz> In-Reply-To: <200912071619.56623.manningc2@actrix.gen.nz> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200912080955.43335.manningc2@actrix.gen.nz> Cc: Jeff Angielski List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Monday 07 December 2009 16:19:56 Charles Manning wrote: > On Monday 07 December 2009 15:27:57 Jeff Angielski wrote: > > I was wondering what type of filesystem everybody is using for the newer > > NAND flash with OOB>=128 bytes. For me, this is the Micron > > MT29F8G08AAA which has an OOB=218. > > > > It seems that the JFFS2 tools are out of date and don't work with > > anything less than or equal to 64bytes of OOB. > > > > YAFFS2 does not compile in the latest kernel source trees (2.6.31 in the > > DENX linux-2.6-denx git tree). Is this filesystem dead? > > Far from it. > I'll take a look at why it does not compile. I just compiled yaffs2 in 2.6.29, 2.6.30, 2.6.31, 2.6.32 from kernel.org. No problems. I didn't try denx. I would suggest you'd get further trying to sort this out in the denx or yaffs lists. > > > As far as I can tell, that only leaves UBIFS. Is UBIFS ready to > > deployed in the field? > > > > Is there any other choice for these parts? > > ______________________________________________________ > Linux MTD discussion mailing list > http://lists.infradead.org/mailman/listinfo/linux-mtd/