RE: [Yaffs] OneNAND

> > It looks like the oob is accessible but in a slightly restriced way.
> > Hopefully this can all be hidden from yaffs per se via the mtd layer.
> > Are there plans to support OneNAND Thomas?
> >
> In principle yes, but I still wait for the Samsung driver to show up or
> a contract to do it myself :)
>
Ok.

> > I note the mtd thread in Feb started by samsung (starting from
> >
> http://lists.infradead.org/pipermail/linux-mtd/2005-February/01186
> 0.html). The mood seemed to be to split off OneNAND from generic
> nand as the access is so different. I was unclear whether this
> presents OneNAND as non generic NAND mtd technology possibly
> requiring changes to yaffs eg the test for the device being an
> "mtd-nand" at mount time.
>
> I'm not sure either. I have just skimmed the datasheet, but it might be
> possible to setup a NAND compatible API
>

It looks like there are only 2 bytes of user usable data in the "spare" area. Although yaffs won't need to do so much ecc it looks like yaffs will have a problem with that little spare space unless one can use bigger virtual blocks. Charles?

Nick

> tglx
>
>
>
> _______________________________________________
> yaffs mailing list
> yaffs@stoneboat.aleph1.co.uk
> http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
> --
> No virus found in this incoming message.
> Checked by AVG Anti-Virus.
> Version: 7.0.323 / Virus Database: 267.7.1 - Release Date: 13/06/2005
>
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.7.1 - Release Date: 13/06/2005