Re: Yaffs2 2.4 support

Sorry if you already know this, but - as far as I can tell, MTD tracks 
seperately from the kernel.  You probably want to get the latest MTD 
from http://www.linux-mtd.infradead.org/ and try to patch your kernel 
with that.

Brad

James Newell wrote:

> I pulled down the 2.4.29 from kernel.org, and the 2.6.9.  Only the 
> 2.6.9 had it.
> I'm currently working 2.4.18 (for company reasons).  It appears that 
> the mtd large block nand support would need to be back ported as well 
> to allow yaffs2 to have large block nand support in this older 
> kernel.  I've read a little of the mtd list, and there seems to be no 
> interest for them to keep the 2.4 kernel support alive.  Do you have 
> any advice on a good snapshot of the mtd driver to back port the 
> 2.4.18 kernel.  They don't appear to have any cvs branches to 
> distinguish from 2.6 support and 2.4.
>
> Thanks,
>
> Jim
>
> -----Original Message-----
> From: Charles Manning [mailto:manningc2@xxxxxxxxxxxxx]
> Sent: Monday, March 07, 2005 6:18 PM
> To: James Newell; yaffs@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: [Yaffs] Yaffs2 2.4 support
>
> On Tuesday 08 March 2005 08:49, James Newell wrote:
> > Yaffs2 is using a mtd 2.6 only structure members called block_isbad,
> > and block_markbad members from mtd_info structure.
> >
> > Is yaffs2 usage of these memebers required for 2.4 kernel support? In
> > other words, am I required to back port the mtd 2.6 kernel driver in
> > order to use
> > yaffs2 in a 2.4 kernel?
>
> Probably, though I thought this was also supported in more recent 
> 2.4.x too.
> I got it going on my 2.4.27-based PC. This should be a pretty simple 
> back-port though.
>
> block_isbad and block_markbad push the bad block marking & detection 
> into the mtd because different devices have different bad block 
> marking strategies.
>
>
> _______________________________________________
> yaffs mailing list
> yaffs@xxxxxxxxxxxxxxxxxxxxxx
> 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.308 / Virus Database: 266.6.2 - Release Date: 3/4/2005
>  
>
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.308 / Virus Database: 266.6.2 - Release Date: 3/4/2005
>