Quote:
Originally Posted by [ACL]
Yeah this isnt gonna work out. just synced and saw the binaries pop up. I'll remove it but have autobuild generate this exactly like you have it. When i sync bootevn i can have the latest recovery copied over this method is kept intact without ballooning up git. For all the developers, well this should be no big deal.. the noobs can suffer. But not sure if you agreed or not, but are we stripping the busybox or not?
which reminds me, we need a new thread. Or another place to have dev discussions .. lol. some of the posts are getting to be ridiculous so ill leave it up to one of the young guns to man one of these threads ..
Ok so im back home.. tired but im not sure if ill get to work on LK tonight like i hoped.. but i'll definitely run some more test for the gsm folks. Also i started using mountable modules like cyanogen. My only prob is its hard to script which modules to load.
For example this is how my modules are being generated now
2.6.27.46-01267-g6900b6e-dirty.sqsh
We cant leave it entirely up to android to mount since i dont think its able to determine the uname to know which modules to load. So unfortunately either the initrd will have to do the dirty work or the sysinit. Sysinit might load too late so this may not work out.
Also i was thinking about what you mentioned before, and copying this one file to system/lib/modules may not be a bad idea. this way our data restore will work flawlessly. we will have to make a way to do kernel upgrades but thats down the road.
|
Yeah, sorry about the binary, I wasn't sure what was needed for autobuild and didn't want it to kick off a bad image or something. Should have asked first, and thanks for removing it.
It looks like recovery doesn't need busybox in /recovery/bin. The recovery.tgz I put in the initrd does not have busybox, and it functions just fine. Initially, I had been including it in the recovery.tgz, so it looks like we still have more headroom available in the initrd if we need it for anything else you'd like to include!
I agree about the forming of a new thread for ROM related issues. I'd like to see LMiller write up a post for FRX05 on NAND since I think he did the majority of the work. I'm having a difficult time getting FRX06 working properly, and I don't know what all you guys did to fix it up.
I really would love to see us move modules into system. I wonder if there is a way to reduce the overall size of our modules. They seem so much larger than the modules for other phones.