2.6.32 Port Status

2.6.32 Status

************Issue list for 2.6.32 kernel port********************
Please update this doc with the results of your work or investigations.

Git for the 2.6.32 kernel: https://github.com/cvpcs/android_kernel_omap/tree/shadow-2.6.32-omap

Currently the two biggest issues are the MMC driver and the framebuffer driver.
It appears that once we get these two issues resolved we might at least have a bootable kernel.

The following is a kmsg from 2.6.32 with i2c debug: http://pastebin.com/zzF4QW0T
######################### Update after display fix: http://pastebin.com/UazQ9Vmh
############## Update 2 after few board file fixes: http://pastebin.com/zKwm9Pey
## Update 3 after changing init to reflect mmcblk1: http://pastebin.com/ZwURQhAg

For comparison here is a 2.6.29 kmsg: http://pastebin.com/b9H2aWNj

******Known issues listed in descending priority(as decided my Dalingrin)*******

-Issue #1 MMC driver. 
Currently little or no twl4030 devices are loading. The twl4030 multidevice controller houses the mmc controller as far as I know.
As defined in the board file (board-encore.c) "tps65921" is the name given to the mmc device and can be seen being registered on the i2c bus
on line 118 of the 2.6.32 kmsg. 
However, what cannot be seen in the log is that I have printk statements all over the mmc initialization functions and none of which get called. 
So, either the entire twl4030 chip or the mmc controller portion is failing somewhere between being registered and initialization.
###Update: Changing an i2c identifier for the twl4030 now gets MMC to at least try to load. In fact, it now recognizes the mmc but does not mount
           or see any partitions. http://pastebin.com/zKwm9Pey
###Update: MMC loads and partitions are recognized however, eMMC is set as mmcblk1 vs mmcblk0. Changing init to reflect this causes a reboot after 
           /system is mounted. http://pastebin.com/ZwURQhAg

############## FIXED ################ -Issue #2 Omapfb   
#As can be seen in the logs, omapfb is not getting started correctly. I believe this is the reason for the garbage on screen after the backlight 
#turns on during boot. I haven't looked into this at all yet so there could be an easy fix.
###Update: Somehow vram was set to 0. Updating this to 8mb results in no more garbage on screen, instead I get a beautiful tux logo. However,
#the display driver then KPs.
#####################################

-Issue #3 Sound
I have disabled the SOC sound codec because it causes a kernel panic. This can be revisted after we solve more prudent issues like those above.

-Issue #4 MUSB
I have disabled MUSB in the config because it also causes a kernel panic. Again, this can be revisted once we solve MMC and the framebuffer.


**************************************************************