[Yaffs] cant mount

Charles Manning manningc2 at actrix.gen.nz
Fri Nov 4 07:17:55 GMT 2005


On Friday 04 November 2005 18:41, yonathana wodeselia wrote:
> Dear All,
> I have a samsung nand chip 512/page and would like to know which yaffs to
> use ? yaffs2 or yaffs .. building yaffs in 2.6 gives me a bunch of warnings
> .. I use cvs versions of yaffs and kernel 2.6.12

I suggest you use the yaffs2 codebase with yaffs1 backward compatability 
settings.

The yaffs1 codebase is pretty much static and uis not as well integrated with 
the kernel tree.

NB You might want the mtd from CVS too, not the stock stuff that comes with 
the kernel.

-- Charles


> CC fs/yaffs/yaffs_ecc.o
> CC fs/yaffs/yaffs_fs.o
> fs/yaffs/yaffs_fs.c:168: warning: initialization from incompatible pointer
> type
> fs/yaffs/yaffs_fs.c: In function `yaffs_readpage_nolock':
> fs/yaffs/yaffs_fs.c:463: warning: implicit declaration of function
> `PAGE_BUG'
> fs/yaffs/yaffs_fs.c: In function `yaffs_internal_read_super':
> fs/yaffs/yaffs_fs.c:1277: warning: unused variable `nBlocks'
> fs/yaffs/yaffs_fs.c: At top level:
> fs/yaffs/yaffs_fs.c:146: warning: 'yaffs_read_super' declared `static' but
> never defined
> fs/yaffs/yaffs_fs.c:1492: warning: 'yaffs_internal_read_super_ram' defined
> but not used
> fs/yaffs/yaffs_fs.c:1496: warning: 'yaffs_internal_read_super_mtd' defined
> but not used
> fs/yaffs/yaffs_fs.c:1562: warning: 'my_proc_ram_write_entry' defined but
> not used
> fs/yaffs/yaffs_fs.c:1636: warning: 'yaffs_proc_ram_write' defined but not
> used
> CC fs/yaffs/yaffs_guts.o
> fs/yaffs/yaffs_guts.c: In function `yaffs_SoftDeleteWorker':
> fs/yaffs/yaffs_guts.c:1119: warning: unused variable `chunkInInode'
> fs/yaffs/yaffs_guts.c:1122: warning: unused variable `tags'
> fs/yaffs/yaffs_guts.c:1123: warning: unused variable `found'
> fs/yaffs/yaffs_guts.c:1124: warning: unused variable `chunkDeleted'
> fs/yaffs/yaffs_guts.c: In function `yaffs_FlushFilesChunkCache':
> fs/yaffs/yaffs_guts.c:3145: warning: unused variable `nBytes'
> fs/yaffs/yaffs_guts.c:3141: warning: 'lowest' might be used uninitialized
> in this function
> fs/yaffs/yaffs_guts.c: At top level:
> fs/yaffs/yaffs_guts.c:1921: warning: 'yaffs_CheckObjectHashSanity' defined
> but not used
> fs/yaffs/yaffs_guts.c:454: warning: 'yaffs_RewriteBufferedBlock' defined
> but not used
> fs/yaffs/yaffs_guts.c:483: warning: 'yaffs_CheckWrittenBlock' defined but
> not used
> fs/yaffs/yaffs_guts.c:2368: warning: 'yaffs_DoUnlinkedFileDeletion' defined
> but not used
> LD fs/yaffs/yaffs.o
> LD fs/yaffs/built-in.o
> LD fs/built-in.o
> GEN .version
> CHK include/linux/compile.h
> UPD include/linux/compile.h
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> KSYM .tmp_kallsyms1.S
> AS .tmp_kallsyms1.o
> LD .tmp_vmlinux2
> KSYM .tmp_kallsyms2.S
> AS .tmp_kallsyms2.o
> LD vmlinux
> SYSMAP System.map
> SYSMAP .tmp_System.map
> OBJCOPY arch/arm/boot/Image
> Kernel: arch/arm/boot/Image is ready
>
> I cant mount the device after this ...
> Is there a fix for these ? Or should i use yaffs2 instead ...
> Thanks
> yonathana



More information about the yaffs mailing list