A few of the design areas needed to be tweaked slightly without significant impact.
The only real significance is that what is termed a yaffs_Inode really becomes an object Id. Where an 'object' is a file, directory, symlink or hard link. This differs from the *nix concept of an inode in that a hard link is not an inode. yaffs_Inode should really be renamed to yaffs_Object to reflect this.
Rge reason for introducing the object is to provide identifiers for the objects stored on NAND. For example, each hardlink (which does not have a distinct inode) needs an object Id for storage on
Pretty much all the guts of the code is there except for:
symlink handling (a doddle)
hard link handling.
some of start-up scanning
ECC on tags
superblock handling (ie hook-up to mtd and the Linux VFS). Some of this code to be pinched from JFFS2.
Some of the code has already been tested.
I will now be testing out the guts on a NAND emulation layer in an application. This provides better debugging. I hope to have this running by 11/03/2002.
Once the guts looks solid on the NAND emulation, I will graft it on to the VFS and mtd - at which point it becomes a real file system.
So far I've logged 90 hours on yaffs. I will not be charging for approx 15 hours I have spent swotting up on the Linux VFS. I still believe this is on budget.