On Wed, Nov 11, 2009 at 01:28:08PM +0800, Westermann Fu wrote:
> Dear Wu, It's cool. But what component plays the role of WinSys on android?
> Talk with hardware using DRM yet? If it is, who loads DRM module? I'm not
> familar with android-x86, I think there is no X11 so there is no DRI
It should b
Hi:
Dear Wu, It's cool. But what component plays the role of WinSys on android?
Talk with hardware using DRM yet? If it is, who loads DRM module? I'm not
familar with android-x86, I think there is no X11 so there is no DRI
architecture yet. And it seems in SurfaceFlinger there is interface for GPU
Hi,
On Tue, Nov 10, 2009 at 03:21:35PM -0700, tom fogal wrote:
> We've got an app we'd like to port to `another' mobile platform,
> but shaders are a sine qua non for us. AFAICT Apple's offerings
> are the only thing on the market which offer anything beyond fixed
> functionality. If it was reas
On Tue, Nov 10, 2009 at 03:21:35PM -0700, tom fogal wrote:
> > This is JFYI, in case someone finds it interesting. I also hope it
> > gives more motivations to test out the opengl-es-v2 branch :)
> This is really cool, Chia-I.
> How does the android-eeepc stack differ from the stock android stack?
Chia-I Wu writes:
> Hi list,
>
> I am working on a project to bring Mesa to Android on x86 (intel)
> netbooks
>
> http://www.gitorious.org/android-eeepc
[snip]
> Android supports OpenGL ES 1.0. So my work is basically opengl-es-v2
> branch, plus support for some new extensions and a new EGL dri
Hi list,
I am working on a project to bring Mesa to Android on x86 (intel)
netbooks
http://www.gitorious.org/android-eeepc
Currently, it can fully accelerate Android window compositor. It
provides seamless integration with the Java binding which allows
existing Android 3D applications to be acc
