Hi Spark. It seems current overlay interface can implemented by using these driver 1. v4l2 output 2. pmem 3. general fb.
According to yourself , which do you prefer ? On Jan 22, 3:37 am, Dave Sparks <[email protected]> wrote: > Yes, the intention with the overlay interface is to be able to support > V4L2 and other overlay hardware. > > On Jan 21, 1:02 am, hanchao3c <[email protected]> wrote: > > > The hardware interface is continue changeing in cupcake branch. > > > The hardware overlay interface has some changes now . > > > libhardware/include/hardware/overlay.h > > > Sample Code : > > hardware/libhardware/modules/overlay/overlay.cpp > > > # The main change list: > > 1. overlay_device are separated as overlay_control_device and > > overlay_data_device > > 2. Data path : remove the swapBuffers , getOffset and getMemory > > Add the dequeueBuffer and overlay_buffer_t ! > > > The old interface is designed for using for pmem, which is like a fb > > driver. > > > The new interface is more nature for using v4l2 output driver. > > > Do it mean v4l2 output driver will be the common item for Android ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
