It isn't really a port when there's a x86_64 build target however I'm completely new to Android.
I'd need to know the basics, that is - bootloader - boot process - what are the images? - partition layout? So like I wrote in the topic the goal is running the x86_64 android build (aosp_x86_64-eng) on a chromebook, namely Acer c720. For bootloader, would grub suffice? I'd imagine yes, since it's able to boot regular Linux kernels, so it has to be able to boot the Android Linux kernel. Furthermore it would probably need an unpacked kernel however there is no kernel.img, so I'm thinking... get the chromebook kernel and "somehow" convert it to an Android compatible kernel (with filesystem), or just take the x86_64 source tree and copy the Chromebook kernel config ~ I'd use just the Chromebook with the original OS but everyone and their mom is using Skype, including my mom, and would make a great replacement for her wireless-only tablet. >From a post from 2009 in this mailing list I read that system.img is mounted on / userdata.img is mounted on /data/ what's cache.img? ramdisk.img is apparently the initramfs that "somehow" needs to be included in the kernel boot process can I just create partitions and dd the contents of those img files? Should I use a different bootloader, uboot? -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
