Quote:
Originally Posted by natemcnutty
Wonder if that's why magldr just uses the zImage and initrd.gz from the first partition. Then you could use the update utility to update them without having to ever flash again.
On a side note, I would double check with the Vogue guys to make sure everything does get wiped when they update their kernel. I'm still wondering if partition tables may have something to do with this. Hopefully I can finally get a break from work and home to actually do some serious testing. I find it really odd that the partition table has two partitions that start at the same location rather than simply erasing the second partition and moving the locations of everything.
|
Magldr is a custom bootloader... It can do about anything.
We are in the same as the Vogue (since we copied it). They need to reflash to upgrade there kernal too. No way around it with out a custom bootloader...
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..
|
GREAT!
If it is possible to write to nand from within that would probably solve our problem. (Maybe)
I will wait for your System.tgz. Did you get data working on it?
That was my problem..
It was stable but with no data.