Am 16.06.2010 um 08:31 schrieb Dr. H. Nikolaus Schaller: > > Am 15.06.2010 um 20:34 schrieb Ruben Viets: > >> Hi Nikolaus, >> >> You already have all sources if you tar xvjf the linux-2.6.24.3 and >> afterwards patch -p1 < patch20080530 + patchv33_withoutyaffs2 > > Ok, this was quite easy. > > I did not find many differnces: > > include/mtd/mtd-abi.h -- different size for oob fields (which may be the > issue) > fs-fs-writeback.c -- different strategy for locking > fs/mpage.c -- "It seems that there is a IO coherent bug in > generic_file_mmap()" > fs/yaffs/* -- about 50% of the files differ > > >> >> Don't need to tar and send my files then. Question is if the below dirs you >> mention are enough. You may need additional files. >> So better start from scratch in a different dir and do a diff with your >> letux-400 development directory. >> >> My latest config (CONFIG_RV9) is located at >> http://projects.kwaak.net/twiki/pub/Epc700/KernelPort26Compiling/CONFIG_RV9 > > Here I did not have CONFIG_MTD_SW_HM_ECC set and none of the VERIFY options > > Now it *appears* to work. There are still some strange messages like > "Freechunks verification failure" but I did not do a flash_eraseall - I just > tried to continue to use the file system created with the broken yaffs2.
Ok, I have erased the minifs partition and mounted as yaffs2. The message has disappeared. But there is a mismatch between used/available blocks and what I see as files (an empty lost+found directory). And 'du' reports 40% used. When initializing as jffs2 I get 8% used and a completely empty device. Or is yaffs inappropriate for small NAND partitions? Nikolaus _______________________________________________ Mipsbook-devel mailing list Mipsbook-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/mipsbook-devel
