Charles Manning a écrit :

>To quote from your previous email:
>yaffs_get_inode for object 146776
>yaffs_read_inode for 146776
>
>Now what is odd to me is that the object being referred to is supposed to be 
>the root object (with an objectId of YAFFS_OBJECTID_ROOT which is 1).
>
>Big question: Why is the object Id 146776?
>
>Are you able to debug a bit more?
> The root object is dev->rootDir and dev->rootDir->objectId should be set up 
>during yaffs_GutsInitialise().
>
>Perhaps yaffs_GutsInitialise() is failing and returning early and the failure 
>is not being handled correctly.
>
>Could you try doing some tracing in yaffs_GutsInitialise()?
>
>Thanx
>
>-- Charles
>
>  
>
Thank you very much ! It works now.

Actually, I don't know why the debug messages don't appear...maybe 
because of my kernel config...

Well, I added some printk, and I had this message : yaffs_ObjectHeader 
should be 512 but is 510.

I found the solution at : 
http://www.aleph1.co.uk/pipermail/yaffs/2004q1/000618.html
I added a __u16 at the end of the yaffs_ObjectHeader structure, and now, 
it works : I can mount the partition, write on it, etc...

I'll be able to test Yaffs in depth now !!

Many thanks.

Regards.
Ludovic.