Your answer lies in UBIFS. There is a port for kernel 2.6.24 up to 2.6.27. UBIFS is JFFS3 if you like - and it does support mmap. If your flash chip is of the NOR-type then YAFFS2 will not work - that is what makes UBIFS so sweet! To set up a UBI volume for UBIFS is bit of a schlep, but once done it is a cool piece of equipment.
On Nov 6, 11:39 pm, Markus <[EMAIL PROTECTED]> wrote: > Hi, > > it is the init process, that cannot start. The kernel is always > booting fine and only the Android init process is not able to do its > job. For yaffs2, the booting process stops like > inhttp://groups.google.com/group/android-porting/browse_thread/thread/d... > - I'm sorry, that I can't post my own message at the moment, but I do > not have access to the hardware right now to flash everything... > > Like in the link above, we get the same problem about the magic > number, while Android tries to load the core.jar file. After 4 tries, > Android resigns and reboots. > > bye > Markus > > On 6 Nov., 17:22, "Gergely Kis" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Could you give more information regarding "Android was not able to > > boot onyaffs2". What were the actual error messages? Did the kernel > > hang, or the init process? > > > Best Regards, > > Gergely > > > On Thu, Nov 6, 2008 at 4:18 PM, Markus <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > as I wrote in Android Internals, we ported Android to an i.MX31. > > > Unfortunately, we have some issues with the file system. > > > If I use NFS as file system with a modified init.rc config, everything > > > seems to work well, but this is no option for us as permanent file > > > system, so we decided to useyaffs2as file system. As this did not > > > work (Android was not able to boot), we changed to jffs2. jffs2 boots > > > fine as long as we use a read-only file system. After booting, we can > > > start many applications, but it seems that those requiring file write > > > operations fail to start, e.g. the webbrowser. If we change init.rc > > > config to give file-write permissions, Android is not able to boot > > > anymore. > > > > So we have decided to use a mixture ofyaffs2and jffs2, after we saw > > > this idea at the armv4 port. The basic idea is, that all mmap > > > operations are done onyaffs2, as jffs2 does not support them. At the > > > moment, we split the file system to two parts: /data is located on our > > >yaffs2partition, everything else on our jffs2 partition. The system > > > boots fine and we can run every application. But now, it is getting > > > confusing: As soon as Android has finished booting, it is impossible > > > to write/delete files in /data/app - if we do, we get a kernel panic, > > > which reports FileObserver to fail. This does not happen, if we do > > > file accesses before Android has finished its booting process. > > > > Remembering that we had some cases, in which it was necessary to start > > > the system with strace running in the background (and discarding the > > > log), I booted theyaffs2/jffs2 system with strace in the background. > > > Now, I am able to access files in /data/app, I just get "syscall: > > > unknown syscall trap 0xe1a00000" reported to my debug console. In this > > > mode, it is also possible to run applications directly from Eclipse on > > > the target device. > > > > So can anybody tell me what is going wrong, if I use ayaffs2only > > > file system? And why does strace heal those problems with ayaffs2/ > > > jffs2 system? It just makes the system slower... > > > > bye > > > Markus --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [EMAIL PROTECTED] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
