View Single Post
  #55 (permalink)  
Old 12-17-2010, 06:46 PM
natemcnutty's Avatar
natemcnutty
VIP Member
Offline
Threadstarter
 
Join Date: Nov 2009
Posts: 845
Reputation: 3070
natemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIPnatemcnutty is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: How To Compile Your Own Kernels, Modules, Tinboot (NAND boot), and More for Begin

Quote:
Originally Posted by maurice.green View Post
Sorry that it has taken me a while to respond. I was trying to incorporate the back light work done by acl into the work that I was doing. Yes I have resolved the MTD issue but I was going further keeping the initrd separate from the rootfs unlike the vogue and loading it in to a separate partition in the nand but merging the rootfs with the system.ext2 and maybe the modules. I haven't decided yet if the modules will run best that way or actually integrated into the kernel. I am testing this for speed. I have found that booting is faster with the rootfs separate from th initrd. Though, yes you could combine them it makes the booting time slower. I have gotten the initrd init down to about ten lines of code, if that. As far as flashing goes - you wouldn't need to unless there was a new kernel. The initrd should not ever need to be modified. I have everything else with rw access so that updates can be done live. As soon as I can get with ACL to resolve the back light issue I should be ready to post. The current nbh size that I am dealing with, between the different builds that I am testing is less that 100 mg which leaves a lot of space for user data. I have gone away from actually mounting the system.ext2 and the data image as the device runs much faster when these files are pre decompressed and integrated into the rootfs which is where they are being mounted anyway.
That sounds absolutely awesome! So if you have rw access, we should be able to do OTA updates where we basically run an update app that downloads the latest update.zip, then restart the phone into recovery mode and apply the update?
Reply With Quote
This post has been thanked 1 times.