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