This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Regard opening second frame buffer

Hi All,

 

I am working on omap4430 (blaze board) platform. I have a query regard opening second frame buffer from android framework code. I have looked into the source and come to the conclusion like as follows:

 

when surface flinger thread starts basically it is trying to intialize the Display Hardware and eventually it went to FramebufferNativeWindow.cpp where it is calling hw_module_get of libhardware to load the HAL module, gralloc which basically open the framebuffer and return framebuffer_cntrl_t structure from there it is intialising windows stuff. My question , I tried with FramebufferNatvieWindow(uint32 dpy) to load respecive framebuffer instead of FramebufferNativeWindow()  but when I am trying to use this call it is not able to return framebuffer_cntrl_t structure and giving the error : could n't open framebuffer HAL module....

Please help me to open the second frame buffer using the framework code(I am using L27.G.4 release). I tried with fbtest programme and able to write to second frame buffer(H/w configuration is fb0-over0-mang0-panel0, fb1-over1-mang2-panel1)

 

 

Thanks & Regards,

Kamal

 

 

 

 

 

  • Let me make sure I understand your post correctly? You have the second LCD running correctly and can draw in it with an fbtest program, but you are unble to open a window on the second lcd by specifying the display in your call to FramebufferNativeWindow?

    I think you can do that, but let me try and find the correct procedure for specifying where a window is opened.

  • Hi Kamalakar,

    By default, android does not support multiple display adapters. As per my understanding, you need to extend the support for multiple display adapters in order to open a window on the second lcd. Another means of achieving it is to extend the FramebufferNativeWindow API to take fb_idx as a parameter to get handle to corresponding frame buffer memory, render the contents on to it, ensure that the second frame buffer is connected to another overlay i.e., overlay1 whose manager is second lcd.

    Thanks & Best Regards,

    Venkat

  • >> I tried with FramebufferNatvieWindow(uint32 dpy)

     

    What is the value of the parameter dpy that you are passing ?