Re: [Yaffs] latest cvs of yaffs2

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Nick Bane
Date:  
To: Nick Bane
CC: Yaffs@Stoneboat.Aleph1.Co.Uk
Subject: Re: [Yaffs] latest cvs of yaffs2
> I am trying to establish a re-port of yaffs2 to 2.4.25-vrs2-tcl1 using
> 2k nand and have come across an unexpected issue.
>
> The port is the current cvs with several modifications.
>
> - #define __user is needed in yaffs_fs.c for 2.4 kernels
>
> - An update to yaffs_mtdif2.c to extract the tags according to the
> current oobinfo for raw oob reads as per Wookeys recent efforts.
>
> - A patch to mtdpart.c to copy the master mtd oobinfo to a slave mtd as
> per later 2.6 kernels without which the slave oobinfo is empty and
> causes grief when mounting a yaffs2 partition. This may be the first
> report of this for the 2.4.25-vrs2-tcl1 kernel.
>
> I compile the kernel with either a Dec 2005 or the latest cvs. The older
> one fails to boot corrctly due to oob alignment but is otherwise ok. The
> new version however seems to corrupt devfs so that when mounting devfs
> (just after yaffs2 is successfully mounted as root) error -2 is returned
> from mount_devfs_fs(). This is *new* behaviour as far as I can see.
>
> Removing the third patch makes no difference.
>
> Has anyone a similar experience?
>

Ignore all this rubbish. The reason for the failure is trivial - devfs
cannot be (re)mounted on /dev in the yaffs2 rootfs as yaffs is admitting
to no /dev due to brokenness. Now for the yaffs2 brokenness.

Nick Bane

> Nick Bane
>
> _______________________________________________
> yaffs mailing list
>
> http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
>
>