On 11/14/2013 7:44 PM, Maupin, Chase wrote:
-----Original Message----- From: Heroor, Siddharth Sent: Thursday, November 14, 2013 12:07 AM To: Maupin, Chase; Hingolikar, Mrinmayee; Dmytriyenko, Denys Cc: [email protected]; Cooper Jr., Franklin Subject: Re: [meta-arago] [PATCH 0/5] GStreamer multimedia framework and plugins recipesOn 11/11/2013 8:05 PM, Maupin, Chase wrote:Mrinmayee, Some things that would help would be if you could give us anidea about the following:1. What are these patches adding? Are they adding newcomponents? 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 separateproject 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 theplan/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 tobeing 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. :-(Not trying to give you flack. Just trying to understand what was going on and if there was a better way to separate this code to make it more portable. Knowing there is a plan to get to 1.x is a good thing and helps us in making a recommendation on how to proceed. I think we can work with these recipes, but they need to be modified to not apply to all devices but instead limit them to your device.
Right. Let's limit the recipes to OMAP5 and J6 but is it possible for it to be built and tested in the Core SDK context? Or do you recommend that we use -glsdk.bb for the recipe and give a preferred provider in the branding file?
Sincerely, Chase Maupin Integration Team Manager Linux Core Product Development e-mail: [email protected] phone: (214) 567-2950 For support: Forums - http://community.ti.com/forums/ Wiki - http://wiki.davincidsp.com/-----Original Message----- From: Hingolikar, Mrinmayee Sent: Monday, November 11, 2013 12:16 AM To: Dmytriyenko, Denys; Maupin, Chase Cc: Cooper Jr., Franklin; [email protected] 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, wehavedecided 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 multimediaframeworkand plugins recipes Mrinmayee, Myself, Franklin and Chase have asked you to estimate theamountandsize of the patches that you have in your gstreamer trees. Andyoustill have not answered that. The reason we are asking this simple question is because thechangesyou are making to the recipes will affect others and cannot beacceptedas is. You would need to use machine override VAR_omap-a15instead ofCOMPATIBLE_MACHINE and depending on the amount and size of thepatches,you either simply apply them just for your machine, or changetheSRC_URI completely for your machine. Either way, I would like to encourage you to participate inthediscussion and not just disappear. Thank you. -- Denys On Fri, Oct 25, 2013 at 12:08:48PM -0400, Maupin, Chase wrote:-----Original Message----- From: [email protected] [mailto:meta-arago-[email protected]] On Behalf Of Cooper Jr., Franklin Sent: Friday, October 25, 2013 10:27 AM To: Dmytriyenko, Denys; Hingolikar, Mrinmayee Cc: [email protected] Subject: Re: [meta-arago] [PATCH 0/5] GStreamer multimedia framework and plugins recipes All of your appends are currently blocking all of thegstreamerplugins for all machines other than omap-a15. There is nowaytoonly apply a bbappend for a specific machine and have allothermachines ignore the bbappend. Depending on your patch set on top of the standard gstreamer sources it probably would be better to break out the patchesfromyour git repo and add it to the SRC_URI for only the omapmachine.This may be preferred just to help keep from getting lockedtoparticulargstreamer version and make clear the changeds on top. Butnumber ofpatchesis something that would weigh in here.Another approach would be to create a "new "recipe calledomap-<base recipe name> that "requires/includes" the basegstreamerrecipe and then you can override whatever you want. Take alook atthe 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 indicatethisisn't the standard gstreamer.If not patches one of the above seems right.Others may have other approaches that they recommend.-----Original Message----- From: [email protected] [mailto:meta-arago-[email protected]] On Behalf Of Dmytriyenko, Denys Sent: Friday, October 25, 2013 5:35 AM To: Hingolikar, Mrinmayee Cc: [email protected] Subject: Re: [meta-arago] [PATCH 0/5] GStreamer multimediaframework andplugins recipes On Fri, Oct 25, 2013 at 03:03:35PM +0530, MrinmayeeHingolikarwrote:This patch-set adds GStreamer framework and its plugins: base, good, bad and ugly. The development trees for all of these components aremainitained atgit.ti.com and they are based on top of the Freedesktopreleases.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.36.bbappend create mode 100644 meta-arago-extras/recipes-multimedia/gstreamer/gst-plugins-good_0.10.31.bbappend create mode 100644 meta-arago-extras/recipes-multimedia/gstreamer/gst-plugins-ugly_0.10.18.bb create mode 100644 meta-arago-extras/recipes-multimedia/gstreamer/gstreamer_0.10.36.bbappend -- 1.7.9.5 _______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago_______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago_______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago_______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
_______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
