On 12/22/2011 12:06 PM, Somebody in the thread at some point said:
Hi Vishal -
Thanks for all the effort you guys put in to get it working. I will try to get a 4.0.1 accelerated build working.
Thanks for looking at it!
Build 4 is based on 4.0.3 in which the dss/dsscomp headers in userspace have been updated to the latest aosp kernel.There are few patches from Lajos molnar which are missing I guess.
Upgrading SGX 1.8 driver to v55175 version we can get 4.0.3 running again.
Here is the kernel tip: http://android.git.linaro.org/gitweb?p=kernel/omap.git%3Ba=shortlog%3Bh=refs...
Okay, I will pick the updated patch and test. I guess this will be an ongoing thing to keep on top of.
I forgot to mention two things
- HDMI Audio is broken atm, Jassi is working on fixing that. Onboard
audio should be fine.
- One of the advantages of running off tracking basis is we inherit all
the goodies from vanilla. In this kernel for Android same as in vanilla you'll find working Panda onboard camera driver and Unified Memory Allocator series among other improvements. In this way we can leverage the work we're doing on vanilla twice, by having it appear automatically at the Android kernel too.
Current tilt-android-tracking / android_omap4_defconfig ...
http://git.linaro.org/gitweb?p=landing-teams/working/ti/kernel.git%3Ba=short...
... is working now at 1080p HDMI accelerated on Build 4. I found two quirks, I think they're related to rootfs status or sdcard prep somehow
- got a lot of "unfortunately xyz has stopped" messages until I changed the wallpaper, which seemed to be "no wallpaper" by default in my case. I changed it to "magic smoke" and all those issues went away. Example crash from logcat below if it means anything
E/AndroidRuntime( 1872): FATAL EXCEPTION: main E/AndroidRuntime( 1872): java.lang.RuntimeException: createWindowSurface failed EGL_BAD_ALLOC E/AndroidRuntime( 1872): at com.android.systemui.ImageWallpaper$DrawableEngine.initGL(ImageWallpaper.java:586) E/AndroidRuntime( 1872): at com.android.systemui.ImageWallpaper$DrawableEngine.drawWallpaperWithOpenGL(ImageWallpaper.java:384) E/AndroidRuntime( 1872): at com.android.systemui.ImageWallpaper$DrawableEngine.drawFrameLocked(ImageWallpaper.java:314) E/AndroidRuntime( 1872): at com.android.systemui.ImageWallpaper$DrawableEngine.onSurfaceChanged(ImageWallpaper.java:260) E/AndroidRuntime( 1872): at android.service.wallpaper.WallpaperService$Engine.updateSurface(WallpaperService.java:673) E/AndroidRuntime( 1872): at android.service.wallpaper.WallpaperService$Engine.attach(WallpaperService.java:760) E/AndroidRuntime( 1872): at android.service.wallpaper.WallpaperService$IWallpaperEngineWrapper.executeMessage(WallpaperService.java:1000) E/AndroidRuntime( 1872): at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:61) E/AndroidRuntime( 1872): at android.os.Handler.dispatchMessage(Handler.java:99) E/AndroidRuntime( 1872): at android.os.Looper.loop(Looper.java:137) E/AndroidRuntime( 1872): at android.app.ActivityThread.main(ActivityThread.java:4424) E/AndroidRuntime( 1872): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime( 1872): at java.lang.reflect.Method.invoke(Method.java:511) E/AndroidRuntime( 1872): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:784) E/AndroidRuntime( 1872): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:551) E/AndroidRuntime( 1872): at dalvik.system.NativeStart.main(Native Method) W/ActivityManager( 1401): Process com.android.systemui has crashed too many times: killing!
- in 1080p, the wallpaper / desktop is vertically misaligned, it appears as if it's drawing from a vertical origin of -300 pixels or something. It's otherwise perfect, and the system tray / clock / navigation buttons appear correctly aligned at the bottom.
- similarly in settings, it does not fill the whole vertical space but stops at the same point the desktop ended, about 300 pixels vertically before it could have.
Otherwise, everything basic seems working fine. Lot of things seem broken atm in the rootfs like wifi but that's understandable given the big change.
-Andy