From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from devils.ext.ti.com (devils.ext.ti.com [198.47.26.153]) by arago-project.org (Postfix) with ESMTPS id 24C5352A66 for ; Thu, 14 Nov 2013 07:07:05 +0000 (UTC) Received: from dflxv15.itg.ti.com ([128.247.5.124]) by devils.ext.ti.com (8.13.7/8.13.7) with ESMTP id rAE7725R008100 for ; Thu, 14 Nov 2013 01:07:02 -0600 Received: from DFLE72.ent.ti.com (dfle72.ent.ti.com [128.247.5.109]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id rAE771gH029631 for ; Thu, 14 Nov 2013 01:07:02 -0600 Received: from dlep33.itg.ti.com (157.170.170.75) by DFLE72.ent.ti.com (128.247.5.109) with Microsoft SMTP Server id 14.2.342.3; Thu, 14 Nov 2013 01:07:01 -0600 Received: from localhost (ileax41-snat.itg.ti.com [10.172.224.153]) by dlep33.itg.ti.com (8.14.3/8.13.8) with ESMTP id rAE771CN008207; Thu, 14 Nov 2013 01:07:01 -0600 Date: Thu, 14 Nov 2013 02:07:01 -0500 From: Denys Dmytriyenko To: Siddharth Heroor Message-ID: <20131114070700.GE15473@edge> References: <20131025093335.GA20172@ti.com> <20131025103440.GB13772@edge> <8F29D6B095ED194EA1980491A5E029710C58765A@DFLE08.ent.ti.com> <7D46E86EC0A8354091174257B2FED101597DC30B@DLEE11.ent.ti.com> <20131030225728.GA24696@edge> <7D46E86EC0A8354091174257B2FED1015980ADA9@DLEE11.ent.ti.com> <52846899.7030100@ti.com> MIME-Version: 1.0 In-Reply-To: <52846899.7030100@ti.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "meta-arago@arago-project.org" , "Cooper Jr., Franklin" Subject: Re: [PATCH 0/5] GStreamer multimedia framework and plugins recipes X-BeenThere: meta-arago@arago-project.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Arago metadata layer for TI SDKs - OE-Core/Yocto compatible List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Nov 2013 07:07:11 -0000 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline On Thu, Nov 14, 2013 at 11:37:21AM +0530, Siddharth Heroor wrote: > On 11/11/2013 8:05 PM, Maupin, Chase wrote: > >Mrinmayee, > > > >Some things that would help would be if you could give us an idea about the following: > > > >1. What are these patches adding? Are they adding new components? > As I mentioned these patches are a result of the GLP work on OMAP4. > >2. If new components are being added why not create a separate project for > >them so that it is easier to work on moving them along with different > >releases of gstreamer? Basically split out the "base" gstreamer and the > >new elements. This way if another group wants to look at supporting a > >different gstreamer version your changes are isolated from the gstreamer > >base. > > >3. For patches against gstreamer elements what is the plan/schedule for > >pushing those patches up to the gstreamer mainline to minimize what is > >being carried? > > > >This basically boils down to what is the roadmap tomorrow to being ready to > >adapt to new gstreamer releases and reduce this patchset? What is the plan > >for handling migrations and is a consolidated code base the easiest way to > >do this? > Interestingly, as an example, the original work on gst-wayland was > part of a separate plugin - gst-ducati. As part of the GLP work, > this was moved to gst-plugins-ugly. Upstream GStreamer have a > proposal for a Wayland Sink that we will need to move to in the > future. So, the way I see it, these are specific to current work and > not a roadmap. > > The choices are either we carry the patches on glsdk staging tree or > we host them on meta-ti as a separate recipe because I see that we > will need to move to GStreamer 1.x in the future regardless. Either > way, we are carrying patches that we inherited and now are getting > flack for someone else not upstreaming them 2 years ago when we > weren't even involved. :-( Understood. Thanks, Sid, for the details. But since we are talking about 200-250 patches, keeping them in metadata would be too much overhead. I guess if it's specific to glsdk, we can have the custom recipes to point to your trees... -- Denys > >>-----Original Message----- > >>From: Hingolikar, Mrinmayee > >>Sent: Monday, November 11, 2013 12:16 AM > >>To: Dmytriyenko, Denys; Maupin, Chase > >>Cc: Cooper Jr., Franklin; meta-arago@arago-project.org > >>Subject: RE: [meta-arago] [PATCH 0/5] GStreamer multimedia > >>framework and plugins recipes > >> > >>I was on a long vacation, so I apologize for the delay in > >>response. > >>Here are the no. of patches on top of standard GStreamer. > >> > >>Gstreamer - 15 > >>Gstreamer base plugins - 56 > >>Gstreamer good plugins - 11 > >>Gstreamer bad plugins - 195 > >> > >>Based on Franklin's suggestions and discussions with Sid, we have > >>decided to create new recipes with unique identifiers, for eg. > >>gstreamer-glsdk. > >>Kindly let me know if this approach is fine with you. > >> > >>Regards, > >>Mrinmayee > >> > >>>-----Original Message----- > >>>From: Dmytriyenko, Denys > >>>Sent: Thursday, October 31, 2013 4:27 AM > >>>To: Maupin, Chase > >>>Cc: Cooper Jr., Franklin; Hingolikar, Mrinmayee; meta- > >>arago@arago- > >>>project.org > >>>Subject: Re: [meta-arago] [PATCH 0/5] GStreamer multimedia > >>framework > >>>and plugins recipes > >>> > >>>Mrinmayee, > >>> > >>>Myself, Franklin and Chase have asked you to estimate the amount > >>and > >>>size of the patches that you have in your gstreamer trees. And > >>you > >>>still have not answered that. > >>> > >>>The reason we are asking this simple question is because the > >>changes > >>>you are making to the recipes will affect others and cannot be > >>accepted > >>>as is. You would need to use machine override VAR_omap-a15 > >>instead of > >>>COMPATIBLE_MACHINE and depending on the amount and size of the > >>patches, > >>>you either simply apply them just for your machine, or change > >>the > >>>SRC_URI completely for your machine. > >>> > >>>Either way, I would like to encourage you to participate in the > >>>discussion and not just disappear. Thank you. > >>> > >>>-- > >>>Denys > >>> > >>> > >>>On Fri, Oct 25, 2013 at 12:08:48PM -0400, Maupin, Chase wrote: > >>>>>-----Original Message----- > >>>>>From: meta-arago-bounces@arago-project.org [mailto:meta- > >>arago- > >>>>>bounces@arago-project.org] On Behalf Of Cooper Jr., Franklin > >>>>>Sent: Friday, October 25, 2013 10:27 AM > >>>>>To: Dmytriyenko, Denys; Hingolikar, Mrinmayee > >>>>>Cc: meta-arago@arago-project.org > >>>>>Subject: Re: [meta-arago] [PATCH 0/5] GStreamer multimedia > >>>>>framework and plugins recipes > >>>>> > >>>>>All of your appends are currently blocking all of the > >>gstreamer > >>>>>plugins for all machines other than omap-a15. There is no way > >>to > >>>>>only apply a bbappend for a specific machine and have all > >>other > >>>>>machines ignore the bbappend. > >>>>> > >>>>>Depending on your patch set on top of the standard gstreamer > >>>>>sources it probably would be better to break out the patches > >>from > >>>>>your git repo and add it to the SRC_URI for only the omap > >>machine. > >>>>This may be preferred just to help keep from getting locked to > >>>particular > >>>>gstreamer version and make clear the changeds on top. But > >>number of > >>>patches > >>>>is something that would weigh in here. > >>>> > >>>>>Another approach would be to create a "new "recipe called > >>omap- > >>>>> that "requires/includes" the base > >>gstreamer > >>>>>recipe and then you can override whatever you want. Take a > >>look at > >>>>>the qt4-embedded-gles_4.8.4.bb recipe. > >>>>>http://arago-project.org/git/?p=meta-arago.git;a=blob;f=meta- > >>>>>arago-extras/recipes-qt/qt4/qt4-embedded-gles_4.8.4.bb > >>>>> > >>>>>Or > >>>>>Create new recipes with some unique identifier to indicate > >>this > >>>>>isn't the standard gstreamer. > >>>>If not patches one of the above seems right. > >>>> > >>>>>Others may have other approaches that they recommend. > >>>>> > >>>>>>-----Original Message----- > >>>>>>From: meta-arago-bounces@arago-project.org [mailto:meta- > >>arago- > >>>>>>bounces@arago-project.org] On Behalf Of Dmytriyenko, Denys > >>>>>>Sent: Friday, October 25, 2013 5:35 AM > >>>>>>To: Hingolikar, Mrinmayee > >>>>>>Cc: meta-arago@arago-project.org > >>>>>>Subject: Re: [meta-arago] [PATCH 0/5] GStreamer multimedia > >>>>>framework and > >>>>>>plugins recipes > >>>>>> > >>>>>>On Fri, Oct 25, 2013 at 03:03:35PM +0530, Mrinmayee > >>Hingolikar > >>>>>wrote: > >>>>>>>This patch-set adds GStreamer framework and its plugins: > >>>>>>>base, good, bad and ugly. > >>>>>>> > >>>>>>>The development trees for all of these components are > >>>>>mainitained at > >>>>>>>git.ti.com and they are based on top of the Freedesktop > >>>>>releases. > >>>>>>Why? How large is the patchset on top of upstream? > >>>>>> > >>>>>> > >>>>>>>Mrinmayee Hingolikar (5): > >>>>>>> multimedia: Add GStreamer multimedia framework. > >>>>>>> multimedia: GStreamer base plugins > >>>>>>> multimedia: GStreamer good plugins > >>>>>>> multimedia: GStreamer bad plugins > >>>>>>> multimedia: GStreamer ugly plugins. > >>>>>>> > >>>>>>> .../gstreamer/gst-plugins-bad_0.10.23.bbappend | > >>25 > >>>>>>++++++++++++++++++++ > >>>>>>> .../gstreamer/gst-plugins-base_0.10.36.bbappend | > >>22 > >>>>>>+++++++++++++++++ > >>>>>>> .../gstreamer/gst-plugins-good_0.10.31.bbappend | > >>20 > >>>>>>++++++++++++++++ > >>>>>>> .../gstreamer/gst-plugins-ugly_0.10.18.bb | > >>23 > >>>>>++++++++++++++++++ > >>>>>>> .../gstreamer/gstreamer_0.10.36.bbappend | > >>16 > >>>>>+++++++++++++ > >>>>>>> 5 files changed, 106 insertions(+) > >>>>>>> create mode 100644 > >>>>>>>meta-arago-extras/recipes-multimedia/gstreamer/gst- > >>plugins- > >>>>>bad_0.10.23 > >>>>>>>.bbappend create mode 100644 > >>>>>>>meta-arago-extras/recipes-multimedia/gstreamer/gst- > >>plugins- > >>>>>base_0.10.3 > >>>>>>>6.bbappend create mode 100644 > >>>>>>>meta-arago-extras/recipes-multimedia/gstreamer/gst- > >>plugins- > >>>>>good_0.10.3 > >>>>>>>1.bbappend create mode 100644 > >>>>>>>meta-arago-extras/recipes-multimedia/gstreamer/gst- > >>plugins- > >>>>>ugly_0.10.1 > >>>>>>>8.bb create mode 100644 > >>>>>>>meta-arago-extras/recipes- > >>>>>multimedia/gstreamer/gstreamer_0.10.36.bbapp > >>>>>>>end > >>>>>>> > >>>>>>>-- > >>>>>>>1.7.9.5 > >>>>>>> > >>>>>>>_______________________________________________ > >>>>>>>meta-arago mailing list > >>>>>>>meta-arago@arago-project.org > >>>>>>>http://arago-project.org/cgi-bin/mailman/listinfo/meta- > >>arago > >>>>>>_______________________________________________ > >>>>>>meta-arago mailing list > >>>>>>meta-arago@arago-project.org > >>>>>>http://arago-project.org/cgi-bin/mailman/listinfo/meta- > >>arago > >>>>>_______________________________________________ > >>>>>meta-arago mailing list > >>>>>meta-arago@arago-project.org > >>>>>http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago > >_______________________________________________ > >meta-arago mailing list > >meta-arago@arago-project.org > >http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago >