Quote:
Originally Posted by [ACL]
Finally stabilised this bad boy. No more reboots, all done via sysinit.rc and its the sexiest thing to be able to mount the sdcard as mass storage.
I'll talk to jonpry about this whole kernel portion poop. When wozzer bricked himself i know he was talking about possibly writing to nand from within android. If this is possible, then all kernel updates can be done from inside without bothering the damn bootloader.
In anycase i'll repost my stuff up tonight and continue working on this. Wifi is still broken for me but i know why. Eventually i think our build will have a set of custom scripts that android will execute on boot. 2 i can think of is setting up the wifi nvram part and the other applying the calib points to the input. This way our initrd remains small since the kernel will only get bigger.
I think we have done a great deal of streamlining and i'll discuss with stinedb about possibly using our sysinit.rc for frx05. This way we will only have to worry about updates and not the build itself.
I'll commit the mtd parts tonight..
|
You're awesome
Also, for calibration, the program we invoke to do the calibration is pretty small and wouldn't really cause problems with initrd or adding it to system. The problem is that I always end up with random text cluttering up the touch points. I'd much rather see an app in Android for calibration so lcd density doesn't mess up calibration. I really agree that the closer we can mimic true android devices, the better experience we are going to get.
On the kernel side of things, I was looking at the work of cedesmith on a bootloader that builds on top of tinboot. He's done some interesting things including the ability to load a kernel from the computer which would absolutely rock. He's designing it for the HD2 crowd, but I think I'm going to play around with it and see what I can learn about it. Might be something useful there
http://forum.xda-developers.com/showthread.php?t=901305