Refer lines 1685-1710 in http://android.git.kernel.org/?p=platform/external/opencore.git;a=blob;f=nodes/pvomxvideodecnode/src/pvmf_omx_videodec_node.cpp;h=ead6d65f91830bcccc6cadf3f0105f61c9f07731;hb=fd46810380dc8857b48fb5100bd359a5a71f85d5.
We have the mechanism in place for the omx components to send a pointer and a length parameters down to the MIOs. -Ravi On Jun 9, 8:24 am, Freepine <freep...@gmail.com> wrote: > If the FD stays unchanged during playback session, perhaps you can also pass > it to MIO via PvmiCapabilityAndConfig interface.You can check how video > display info get passed to androidSurfaceOutput. > > On Tue, Jun 9, 2009 at 5:00 PM, manish <android.mm....@gmail.com> wrote: > > > Hi > > > I saw discussion where renderer allocates memory to be used by > > decoder. > > I would like to pass pmem fds from omx component to MIO. [ a specific > > custom audio MIO] . Can some one elaborate on the omx->pv and pv->Mio > > interface changes to achieve something like this ? ideal thing would > > be to get fd as a parameter along with data pointer , data length , > > cmdid, timestamp etc in MIO through the writeasync call. and then > > again , it is needed only for a specific MIO implementation, without > > having to change writeasync api for others. > > > thanks --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
