From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org
Cc: Jeff Angielski <jeff@theptrgroup.com>
Subject: Re: What filesystem for NAND flash with OOB 218
Date: Tue, 8 Dec 2009 09:55:43 +1300 [thread overview]
Message-ID: <200912080955.43335.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <200912071619.56623.manningc2@actrix.gen.nz>
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/
next prev parent reply other threads:[~2009-12-07 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 2:27 What filesystem for NAND flash with OOB 218 Jeff Angielski
2009-12-07 3:19 ` Charles Manning
2009-12-07 20:55 ` Charles Manning [this message]
2009-12-08 3:40 ` Jeff Angielski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200912080955.43335.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--cc=jeff@theptrgroup.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox