Another addition: the headers found in the mtd5 partition were indeed JFFS2 status bits; somehow I messed up the timestamp of the corresponding source file such that the mount in my application was still done because the file was not re-compiled. Now that I deleted this object file of the application the flash sectors remain empty - but obviously now I always have the additional, too long delay during kernel startup.
Still I do not understand which part of the kernel is responsible for the additional delay in case these status bits are not initialized? Is there any scan of the MTD sectors done, and if so, where does it take place? Please, any help is appreciated! Regards, Wolfgang _______________________________________________ uClinux-dev mailing list [email protected] http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by [email protected] To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
