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 be noted that, a DRI driver does not talk to an X11 server.
It talks to its loader.  In X11 environment, the loader talks to the
server in DRI protocol.  This way, a DRI driver is window system
neutral.  It is thus possible to write a new loader that talks to
Android.  This is what egl_android does.  Another good example is
Wayland and eagle.  Actually, egl_android is based on eagle.
> architecture yet. And it seems in SurfaceFlinger there is interface for GPU
> accleratable surface, why not use it directly?
I do implement GPUHardwareInterface with GEM.
> In your mail, you mentioned the window compositor(server), do you refer to
> Surface Flinger or Window Manager Service? My understanding is
> WindowManagerService allocate surface but SurfaceFlinger do the final
> composite operation, is it right? But it seems not all surfaces been
> composited with Opengles, most are directly bitblt, are you acclerating all?
I was referring to SurfaceFlinger.  Surfaces, and the backing buffers,
are allocated and composited by SurfaceFlinger.  When the platform has a
2D blitter (capable of blending, scaling, etc.), SurfaceFinger tries it
first before resorting to OpenGL ES.  It is because the blitter is said
to be faster than the 3D hw on G1 phones.  Since there is no such
blitter on my test platform, all compositions are done with OpenGL ES.

-- 
Regards,
olv

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to