Hi Robin ,
Thanks for your valuable suggestions . It was very helpfull .

I understand that the following things need to be done .

1) Instead of mGraphicsPlane, take array of GraphicsPlane,
   mGraphicsPlane[2] //for 2 displays fb0 and fb1
2) Change the DISPLAY_COUNT value in surfaceflinger.cpp to 2
   #define DISPLAY_COUNT       2
3) Firstly Initialize main display DisplayHardware by passing dpy as
0
   , then secondary DisplayHardware by passing dpy as 1.
4) From init of DisplayHardware pass dpy to EGLDisplaySurface's
mapFrameBuffer and based on dpy value to open /dev/fb0 or /dev/fb1
respectively .
5)Then I need to modify the threadLoop for each of the APIs such as
handlePageFlip() etc .

 Please let me know if my understanding is right ? Do I need to do
anything else .

My Basic Doubt is how can we enable or disable  Second
DisplayHardware instance based upon dpy=0 and dpy =1 passed from the
client ?

How do I  Add a new interface API to the surfaceflinger so that
secondary display could be initilized as and when required ?


Thanks and Regards,
Nikhil



Second  DisplayHardware instance based upon
dpy=0 and dpy =1 passed from the client

On Oct 21, 1: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/c...http://groups.google.com/group/android-porting/browse_thread/thread/6...
>
> 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- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to