Hi Charles. Have you tried this patch? Because I've recieved kernel panic error when I'm trying to mount yaffs2 filesystem throught read_oobfree (I changed read_oob on read_oobfree in the yaffs_mtdif2.c). Thank you, Yuri Golovach yaffs-request@stoneboat.aleph1.co.uk Sent by: yaffs-bounces@stoneboat.aleph1.co.uk 27.01.2006 14:00 Please respond to yaffs@stoneboat.aleph1.co.uk To yaffs@stoneboat.aleph1.co.uk cc Subject yaffs Digest, Vol 8, Issue 20 Send yaffs mailing list submissions to yaffs@stoneboat.aleph1.co.uk To subscribe or unsubscribe via the World Wide Web, visit http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs or, via email, send a message with subject or body 'help' to yaffs-request@stoneboat.aleph1.co.uk You can reach the person managing the list at yaffs-owner@stoneboat.aleph1.co.uk When replying, please edit your Subject line so it is more specific than "Re: Contents of yaffs digest..." Today's Topics: 1. Re: [PATCH] treat OOB as a single chunk of oobavail bytes (Charles Manning) ---------------------------------------------------------------------- Message: 1 Date: Fri, 27 Jan 2006 11:26:23 +1300 From: Charles Manning Subject: [Yaffs] Re: [PATCH] treat OOB as a single chunk of oobavail bytes To: linux-mtd@lists.infradead.org, yaffs@stoneboat.aleph1.co.uk Cc: yuri.golovach@mindspeed.com, Vitaly Wool Message-ID: <200601271126.23808.manningc2@actrix.gen.nz> Content-Type: text/plain; charset="iso-8859-1" On Friday 27 January 2006 01:51, Vitaly Wool wrote: > Hi Yuri, > > well, lemme just summarize what you hafta do in order to make YAFFS2 > work with my patches. > > 1. Apply the following patch to the mtd code: > http://lists.infradead.org/pipermail/linux-mtd/2005-December/014648.html > (yes, it's a single patch!) > 2. Modify the fs/yaffs2/yaffs_mtdif2.c to use read_oobfree/write_oobfree > where appropriate. > > Hope that helps, > > Vitaly Hi Vitaly Is this in CVS yet? If not, I hope it will be there soon. >From what I see, this is going to be just what we need. YAFFS2 does not need to write_oobfree as a seperate function (it is always written as a single page write). YAFFS2 only needs read_oobfree. However, YAFFS1 could use the write_oobfree function at some future date if YAFFS1 gets moved to this interface to remove the current reliance on hanging the ugly ECC parameter stuff through the interface. I am pretty busy right now, but will try get the YAFFS2 side sorted ASAP. If the YAFFS2 stuff is CVSed before the mtd then I'll just point people to this patch. Thanx! Charles ------------------------------ _______________________________________________ yaffs mailing list yaffs@stoneboat.aleph1.co.uk http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs End of yaffs Digest, Vol 8, Issue 20 ************************************