Intel CedarTrail Graphics Support

[diznave]

Hi, 

I am using a Cedar Trail-based Atom platform which contains the GMA3650 GPU with Android-X86.

Right now, I have the UVESAFB driver functioning, but it is a bit slow.  I don't need video playback, but would like the screen transitions to be faster.

I have been able to integrate the GMA3650 Framebuffer driver from the 3.3.6 Linux kernel, and it does appear to start up at the second stage of the debug startup sequence.  

When I start up Android, I will get a normal Android screen and a constant "Unfortunately, System UI has stopped" message.  It's almost like the draw operation occurs, but doesn't notify the UI system that it has completed.

I understand that Mesa sits between Android and the driver, but I'm not exactly sure where to start.  It sounds like Mesa does not yet support the GMA3650 (?).  

If anyone has experience in understanding how the different subsystems come together in for UI/Graphics, I would greatly appreciate any information.  I would be glad to contribute my findings back to the community here.  

Thanks

-dave

[diznave]

Thank you for the feedback.  I'm going to go through this and see what I might be able to find. 

The diagram of how Mesa interfaces with Android was extremely helpful and I appreciate your input.  

It sounds like the Meego release of Linux is where I want to start from to see if I can find the appropriate changes.

I will let the group know if I can make this work.

On Thursday, May 17, 2012 1:37:31 PM UTC-4, tabletsx86 wrote:

also check this:

   http://ubuntuforums.org/showthread.php?t=1953734&highlight=intel+gma+3650&page=3

[Dan]

You should give it up right now trying to get Cedar Trail working.
Without Intel support on that binary only driver for the PowerVR GPU
in Cedar Trail, it will never work. this is mentioning in that doc
from above: Not supported: ZXXX, E6XX, and the N2600 N2800 series as
well. There is no documentation for the GPU or the driver. You'd be
better off getting another motherboard.

[dspt1]

It's certainly a difficult road- I am trying to make this work on a particular platform so changing motherboards is not really an option.

I have been able to make the Meego Graphics driver start up with Android-x86, but I still get a terrible frame rate (System UI not responding)-- I'm not sure the reason for this.  I don't yet understand how Android bypasses Mesa when using the UVESA driver.  I would at least like to get as good performance with either the new Linux GMA3650 driver or the Meego driver as UVESA, but it's still not there.

The folks at Archermind have apparently made Gingerbread function on Tunnel Creek (SGX535) which may provide clues on making it work for Cedar Trail (SGX545) [http://www.archermind.com/download_android/].

And Chih-Wei, Thank you so much for that presentation-- it is very helpful.

[dspt1]

I see it now- when UVESA is loaded, HWACCEL gets set to 0.  If I pass HWACCEL=0 at the command line, the performance is still bad but it does not pop up the "System UI is not responding" message.  

[Dan]

You can try that Gingerbread BSP, but I've done that, and when you're
finished, you'll want those few days of your life back. Until
something changes from Intel on those ZXXX, E6XX, and the N2600 N2800
GPUs, I would still recommend you look elsewhere.