[Gstreamer-openmax] [PATCH] a small bit of refactoring to gstomx_util, to allow for more flexibility of when the OMX component and port is instantiated

Stefan Kost ensonic at hora-obscura.de
Mon Nov 23 14:12:06 PST 2009


hi,

Rob Clark schrieb:
> On Nov 14, 2009, at 6:33 AM, Felipe Contreras wrote:
> 
>> On Fri, Nov 6, 2009 at 4:58 AM, Rob Clark <rob at ti.com> wrote:
>>> On Nov 5, 2009, at 10:56 AM, Felipe Contreras wrote:
>>>> It's not required right now, is it? The component_name and
>>>> library_name are only needed in the _init function.
>>> But the point of this patch was that _init() could be called upon  
>>> demand the
>>> first time the element needs to access the handle.  So they might  
>>> be needed
>>> earlier than when _init() was traditionally called.
>> I sent a reply to your personal mail explaining why this is a
>> fundamental change, and we should probably wait until we have an omx
>> registry implemented.
> 
> 
> yeah, I'm starting to get your point about needing a registry..  it  
> might be another month or so before I have much time to work on it,  
> but I'd be happy to implement some sort of registry / config-file when  
> I do have a bit more time.
> 

It might be totally off topic, but are you aware that you can have custom data
in gstreamers registry. gst_plugin_{set,get}_cache_data allows you to store a
hierarchic structure within the registry.

Stefan




More information about the Gstreamer-openmax mailing list