I just checked in a change into our internal tree this morning that
moves just a few functions that are specific to the pmem
implementation into a separate subclass. This change should be go out
in the next batch migration within 2-3 days.

With this change, the generic MIO will use the OpenCore codecs, color
convert to RGB565 and push the buffers to SurfaceFlinger. It also
falls back to this behavior if you are running device specific code in
the emulator.

If you want a hardware specific module, you create a subclass of
AndroidSurfaceOutput and a factory function to create it and include
it in a new library called "libopencorehw.so". When PlayerDriver
constructs the video MIO, it dlopen's the hardware library and calls
the factory function to create the MIO. If any of those steps fails,
it falls back to the generic MIO.

On Jan 26, 11:42 am, Archer <archerstark...@gmail.com> wrote:
> Hi Dave,
>
> Is there any new update about this hardware abstraction? Is it
> available soon?
>
> So right now, by default the generic MIO is being used. then is
> hardware accelerated rendering (and color conversion) still enabled
> with generic MIO? Or it is completely independent?
>
> Thanks,
> Archer
>
> On Jan 20, 8:24 am, Dave Sparks <davidspa...@android.com> wrote:
>
> > Yes, we are providing hardware abstraction for video sink and adding
> > support for video overlays.
>
> > On Jan 20, 3:53 am, Freepine <freep...@gmail.com> wrote:
>
> > > oh? for hardware overlay?
>
> > > 2009/1/20 hanchao3c <hancha...@gmail.com>
>
> > > > It seem video MIO has add a new impl too
>
> > > > I think Spark should know it .
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"android-framework" group.
To post to this group, send email to android-framework@googlegroups.com
To unsubscribe from this group, send email to 
android-framework+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to