Openembedded Core Discussions
 help / color / mirror / Atom feed
From: alexander.kanavin@linux.intel.com
To: "Yuqing Zhu" <b54851@freescale.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [poky][PATCH 00/13] Add patches for gstreamer 1.6
Date: Mon, 18 Jan 2016 19:16:07 +0200 (EET)	[thread overview]
Message-ID: <56864.10.252.12.252.1453137367.squirrel@linux.intel.com> (raw)
In-Reply-To: <1453109582-25485-1-git-send-email-b54851@freescale.com>

> ---gstreamer1.0
>    Correct the setting for FLAG_DISCONT when push to adapter.
>
> ---gstreamer1.0-plugins-base
>    Fix taglist not being sent to down stream issue.
>    Fix audio/video decoder error.
>    Make gstaudiobasesink print warning instead of returning ERROR.
>    Disable orc optimization for lib video.
>    Add video crop supporting when convert frame.
>
> ---gstreamer1.0-plugins-bad
>    Fix mpegtsmux get wrong pid.
>    Add code type checking in mpeg4videoparse when draining.
>    Detect picture coding type when draining.
>    Fix frame rate info lost when fixating caps.
>    Add video stitching support based on Open CV.
>    Fix memory leak of navigation thread in glwindow.
>    Fix loop test hang in glimagesink.

Please explain what is the benefit of having these patches in oe-core
right now, instead of just getting the fixes automatically from future
upstream releases. Why are you submitting these patches in particular, are
they something that a lot of people will benefit from?

These patches add significantly to the maintenance burden of oe-core
recipes, and if they're difficult to forward port, they will simply be
dropped from the recipes when new versions of gstreamer are out.

Generally, we prefer to take patches that:
a) fix build issues, particularly those exposed by cross-compilation or
less common architectures.
b) fix issues that are embedded-specific.


Alex


      parent reply	other threads:[~2016-01-18 16:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-18  9:32 [poky][PATCH 00/13] Add patches for gstreamer 1.6 Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 01/13] gstreamer1.0: [baseparse] unset FLAG_DISCONT when push to adapter Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 02/13] gstreamer1.0-plugins-base: Fix taglist not being sent to down stream if all the frame corrupted Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 03/13] gstreamer1.0-plugins-base: Fix audio/video decoder error Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 04/13] gstreamer1.0-plugins-base: Make gstaudiobasesink print warning instead of returning ERROR Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 05/13] gstreamer1.0-plugins-base: Disable orc optimization for lib video Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 06/13] gstreamer1.0-plugins-base: Add video crop supporting when convert frame Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 07/13] gstreamer1.0-plugins-bad: Fix mpegtsmux get wrong pid Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 08/13] gstreamer1.0-plugins-bad: Add check coding type when drain in mpeg4videoparse Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 09/13] gstreamer1.0-plugins-bad: Detect picture coding type when drain Yuqing Zhu
2016-01-18  9:32 ` [poky][PATCH 10/13] gstreamer1.0-plugins-bad: Fix frame rate info lost when fixate caps Yuqing Zhu
2016-01-18 15:04   ` Burton, Ross
2016-01-18  9:33 ` [poky][PATCH 11/13] gstreamer1.0-plugins-bad: Add video stitching support based on Open CV Yuqing Zhu
2016-01-18 15:10   ` Burton, Ross
2016-01-18  9:33 ` [poky][PATCH 12/13] gstreamer1.0-plugins-bad: Fix memory leak of navigation thread in glwindow Yuqing Zhu
2016-01-18 15:05   ` Burton, Ross
2016-01-18  9:33 ` [poky][PATCH 13/13] gstreamer1.0-plugins-bad: Fix loop test hang in glimagesink Yuqing Zhu
2016-01-18 15:08   ` Burton, Ross
2016-01-18 17:16 ` alexander.kanavin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56864.10.252.12.252.1453137367.squirrel@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=b54851@freescale.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox