In reply to the previous page, I'd be down for a step by step that starts from having a working Moboot/CM9/WebOS install.
It's really simple, you can follow the CM9 instructions and then follow the Ubuntu instructions after that, they do not interfere with each other. The only issue is the /boot partition, which is a 32MB-ish partition on the internal SD card that stores the OS kernels for booting. There is enough room for WebOS stock kernel, CM9 stock kernel, ClockWorkMod Recovery, and Ubuntu kernel all at once, but if you start adding modified WebOS or CM9 kernels you can overflow /boot (bad idea, don't do it). To see how much space is used in /boot, under WebOS type 'df' in a terminal (either XTerm or Novaterm works) and the first entry should be /boot, telling you the disk usage on that partition.
silverword said:
how compiling your kernel 3.0 and informations about the tools you use to compile, compiler version, platform (PC, MAC, Touchpad)
I'm using Ubuntu 12.04 in a VirtualBox on Win7 64-bit (though that doesn't make a difference, you can use any Linux with the right compilers installed). I'm using Ubuntu's default ARM compiler (arm-linux-gnueabi-gcc) though if you compile natively on the TouchPad itself the standard GCC is for ARM instead of x86. The kernel tree is from jcsullins'
kernel-tenderloin-3.0 repository, staging2 branch. I'm still messing around with config options to make it work correctly, it isn't usable yet. The working kernel I posted last night was 2.6.35.
What works on 3.0 and what doesn't:
- Frame buffer console works
- LVM mount and booting Ubuntu works
- X server starts to Ubuntu 12.04 log-in page (using freedreno driver)
- Framebuffer colors are swapped (red and blue channels, but I have a fix for this)
- USB host does not work (so no keyboard/mouse)
- Touch screen does not work (due to I2C errors)
- USB client (Android gadget) works, so you can adb in for a shell
- Bluetooth untested
- WiFi does not work (though only because I haven't tried compiling modules, it should work fine once I do that)
I'm also concerned about audio, and looking for anyone who has any information about getting proper ALSA support on the msm-audio interface which doesn't get detected by ALSA mixer. From what I've read, Qualcomm's audio driver is not a complete implementation of ALSA, only the bits that Android requires.