On 3/28/07, Johann Kok (JP) <
KokJP@telkom.co.za> wrote:
> If I interpret the answer to that post correctly, all I need to do is
> set the correct geomery parameters in yaffscfg.c (including
> isYaffs2=0) and write a low-level driver for the new chip that will
> implement the yaffs1 access functions (writeChunkToNAND,
> readChunkFromNAND, eraseBlockInNAND, initialiseNAND, markNANDBlockBad
> & queryNANDBlock) instead of the (current) yaffs2 functions.
No, that's completely wrong. Just enable the config options that turn
YAFFS1 support WITHIN YAFFS2 on, and optionally auto-select YAFFS1/2
depending on the page size, just not to bother, and that should be it.
vitaly
(text/plain)