Hello! I am interested in testing this on my Palm Tungsten T3, but i have a few questions. I am familiar with the hackndev palm linux, and have used it before, but not cocoa boot (was using gurax), and the packages were pre-built. I am guessing i need to build the root fs from git.
Is there a git tree with the changes you have applied already? How big of an SD card do i need? Do i build directly on the SD or in the git folder on my computer then copy everything over to the second partition of the SD card? What are the commands to put into cocoboot to make it boot (on a t3, guessing similar ram to treo) Thanks in advance On Tue, Dec 30, 2008 at 10:19 PM, Lo Yuk Fai <[email protected]> wrote: > > Greetings! > > > What source are you using? android.git.kernel.org? hackndev? > > Are there any patches you've applied? > > The kernel is based on the android.git.kernel.org tree. > > Then I used git to get a diff between the stock and H&D's 2.6.27 > kernel trees, and patched the above mentioned tree accordingly. > > I uploaded the diff to http://www.mediafire.com/?1x9jnigundy > > Afterwards, run "make palmt650_defconfig" to get a default .config. > IIRC, Thumb support is not enabled so you need to configure it > manually. You may also enable the Low Memory Killer. > > > What does the command look like to cross-compile to the ARM > > architecture? > > The Android sources include the ARM cross-compiling toolchains > already. I had also installed the CodeSourcery toolchains from > http://www.codesourcery.com/gnu_toolchains/arm/download.html > > > Using cocoboot? > > Yes sure. > > > Did you manage to get dropbear installed? Can you connect to the > > phone from your PC? > > Not yet tried. > > > After you've got the kernel, you can then partition the SD card into 2 > partitions, 1 FAT for the zImage and 1 ext2/ext3 for the Android. You > can try running the Android init command directly by giving cocoboot > the command line "rootdelay=1 root=/dev/mmcblk0p2 init=/init". > > For some reasons I only managed to do it with the pre-cupcake build, > but not the post-cupcake build (there are some permissions errors... I > think the reason is not because of Android but I haven't yet figured > it out). Anyway I made the Android binaries into system.img and > data.img, used a initrd.gz and mount them as loop devices on boot, > then load the Android init. > > Hope this helps. > > On Dec 31, 7:54 am, Don Spaulding <[email protected]> wrote: > > Lo Yuk Fai wrote: > > > I just compiled and booted the new codes/binaries on my Treo 650, > > > unfortunately it's still in a loop and no-go. > > > > > Could someone enlighten me on the debug process...? > > > > Greetings Lo (and other Android on Treo hackers)! > > > > I'm a long-time linux user, first-time kernel compiler, so this whole > > process is a bit foreign to me. I'd like to get at least to the point > > that you're at to see what I can do to help. Can you provide just a > > brief overview of how you got to where you are right now? I've got > > the Android master branch downloaded (http://source.android.com/download > > ) and built against the generic target ($ make), but I'm a little > > unsure where to go from here. Specific questions I have are... > > > > What source are you using? android.git.kernel.org? hackndev? > > > > Are there any patches you've applied? > > > > What does the command look like to cross-compile to the ARM > > architecture? > > > > Using cocoboot? > > > > Did you manage to get dropbear installed? Can you connect to the > > phone from your PC? > > > > I'd be grateful for any assistance, I'll try to stick around #android > > and #hackndev if IRC is more convenient. > > Don Spaulding > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
