#12491 HIGH 13.1.0: Implement vMeta for XO-4

[Zarro Boogs per Child]

#12491: Implement vMeta for XO-4
---------------------------------+------------------------------------------
           Reporter:  dsd        |       Owner:  jnettlet     
               Type:  defect     |      Status:  new          
           Priority:  high       |   Milestone:  13.1.0       
          Component:  kernel     |     Version:  not specified
         Resolution:             |    Keywords:               
        Next_action:  never set  |    Verified:  0            
Deployment_affected:             |   Blockedby:               
           Blocking:             |  
---------------------------------+------------------------------------------

Comment(by dsd):

 Providing vmeta for gstreamer-0.10 should be easy.

 For gstreamer-1.0, it looks like it would be at least a few hours work to
 port the code, plus a suitably large amount of time for
 testing/debugging/fixing. Here is a good reference:
 http://cgit.freedesktop.org/gstreamer/gstreamer/tree/docs/random/porting-
 to-1.0.txt

 I've attached an patch for initial porting of gstvmetadec. There are quite
 a few big things left to port. vmetadec_push_frame_to_downElement needs to
 use the GstMemory API (e.g. gst_memory_new_wrapped) to feed memory into
 the GstBuffers that it creates, and probably use the GstMemory
 GDestroyNotify for freeing. For IPPGST_BUFFER_CUSTOMDATA we can probably
 use gst_mini_object_set_qdata on the GstBuffer.
 Then there are a load of pad and caps API users to fix up as well.

 Not to forget the vmetaxv code that will probably need similar treatment.

 I suggest that we continue focusing on the XO-4 graphics driver and other
 priority items, and when things are stable, reinstate vmeta on
 gstreamer-0.10. When we are that far, we can revisit providing vmeta for
 gstreamer-1.0. As we currently don't integrate vmeta into the release, we
 are not bound by the usual deadlines, we just have to try and complete the
 work by the time that customers recieve machines.

 If we don't provide vmeta for gstreamer-1.0, a deployment that wants to
 use vmeta in Jukebox can can probably just use the Jukebox version from
 12.1.0. Not ideal, but it should work. We'll have to give that a quick
 test.

-- 
Ticket URL: <http://dev.laptop.org/ticket/12491#comment:2>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system