Hi Robin, Your suggestions before are very helpful for me. And I have some questions here: In readyToRun() of surfaceflinger.cpp , I intialize the graphics device 1 and 2 simultaneously, however it seems that hw.makeCurrent() only can bind one single thread, and only the last graphic device binded is successfully.(Now I have no this kind of device with two displays, so I modify the qemu, and add another framebuffer device to emulator, and it can work normally ). My question is if it's necessary to add an interface to make Surfaceflinger hold two thread like AudioFlinger?
Thanks and regards bigcren On Wed, Oct 21, 2009 at 4:26 PM, Robin Gujjar <[email protected]>wrote: > > Hi Nikhil, > > You have to modify the surfacefilnger and UI code for Fb1 > initialization, you will find some comment in surafceflinger.cpp for > FB1 initilization( DisplayHardware instance for FB1 on the basis of > dpy value). And u have to modify the EGLDislaySurface.cpp also. Other > modification is alos there please read the below post for more > information . > > > http://groups.google.com/group/android-porting/browse_thread/thread/c726d1258955314d > > http://groups.google.com/group/android-porting/browse_thread/thread/6b9e7547de761f0a > > thanks and regards > Robin Singh > > > > On Oct 20, 8:01 pm, nikhil <[email protected]> wrote: > > Hi , > > > > Can anybody tell us the exact modification required in SurfaceFlinger > > and the corresponding UI code for supporting multiple framebuffer > > device (/dev/fb0 and /dev/fb1) . > > > > Idea is that the other display should be initialized asynchronously, > > so that it could come and go > > > > Thanks in advance for all the help . > > Regards, > > Nikhil > --~--~---------~--~----~------------~-------~--~----~ > unsubscribe: > [email protected]<android-porting%[email protected]> > website: http://groups.google.com/group/android-porting > -~----------~----~----~----~------~----~------~--~--- > > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
