Hi Dianne, We have hardware acceleration support and that supports multiple frame buffer device display ( as we have tested it with driver test application). but how to fit that into SurfaceFlinger is the issue. As per our study and understanding of SurfaceFlinger we have done few changes as below: 1: Instead of mGraphicsPlane, take array of GraphicsPlane, mGraphicsPlane[2] //for 2 displays fb0 and fb1 2: First Initialize main display DisplayHardware by passing dpy as 0 (Modified the constructor of the Display Hardware), then secondary DisplayHardware by passing dpy as 1. 3: From init of DisplayHardware pass dpy to EGLDisplaySurface's mapFrameBuffer and based on dpy value open /dev/graphics/fb0 or fb1. 4: Add a new interface API to the surfaceflinger so that secondary display could be initilized as and when required. 5: Modified the threadLoop so that each of the APIs handlePageFlip(), handleRepaint(), unlock Clients() will be called for both displays dpy-0 and dpy-1.
There are following issues that I am not that much clear. 1: Does we need to modify the OpenGL|ES initialization based on the DisplayId (dpy) or it will remain same for both display? 2: Does any chnage in the libagl is required for support of multiple frame buffer support? 3: We have kept the mWormHoleRegion separate for both GrpahicsPlane (0 and 1), so whether we require to maintain different mDirtyRegion and mInvalidate region for both GrpahicsPlane? 4: How the Layer created on different grphics plane will be composed to display on the same physical screen? It will be nice if you can focus some more light on the above issues. Thanks and Regards, Pankaj Dubey On Sep 16, 1:34 am, Dianne Hackborn <hack...@android.com> wrote: > Hi, these kinds of questions should be posted to android-porting. > > And I think you are looking at a pretty serious change, especially if you > intend to have a production quality result that supports hardware > acceleration. > > On Mon, Sep 14, 2009 at 10:52 PM, Robin Gujjar <robin.guj...@gmail.com>wrote: > > > > > Hi All, > > > As suface flinger uses fb0 for rendering the image and video. i want > > to change the frame buffer devices dynamically for rendering the image > > on the screen one time on Fb0 other time on Fb1. i am looking into the > > surface flinger code. but we are not able to get the pointer where to > > change for this. can simeone please give us some pointer. > > > thanks > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
