Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gstreamer1.0-plugins-bad: change glimagesink rank to marginal
Date: Fri, 25 Sep 2015 13:34:56 +0300	[thread overview]
Message-ID: <56052350.9070405@linux.intel.com> (raw)
In-Reply-To: <CAP71Wjz0zd_gTE8J82P0bvxvqSb_iH2CkK5jy=sGUGjKk_dGSQ@mail.gmail.com>

On 09/24/2015 11:03 PM, Nicolas Dechesne wrote:

> fwiw... on my platforms (QCOM DragonBoard) I rely on glimagesink, and
> we have good OpenGL support.. but I understand that this isn't the
> norm for ARM, and more an exception.. I can manage that in my BSP
> layer, if that ever gets merged. Note we might want to wait for the
> upstream discussion to settle before merging.

If you explicitly specify glimagesink in your pipelines, then this patch 
will not affect you. But if you rely on gstreamer's autoplugging, then 
it's entirely coincidental that you're getting the sink you want; 
gstreamer makes no promises about what you end up with. It simply sorts 
sinks by their hardcoded rank, and picks the first one that initializes 
without error.

The upstream discussion has stalled two months ago. Meanwhile we have a 
real problem in qemu images: video playback does not work. If you can 
propose a better fix, you're very much welcome.


Regards,
Alex



      parent reply	other threads:[~2015-09-25 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 17:42 [PATCH] gstreamer1.0-plugins-bad: change glimagesink rank to marginal Alexander Kanavin
2015-09-24 20:03 ` Nicolas Dechesne
2015-09-24 20:19   ` Burton, Ross
2015-09-24 22:26     ` Nicolas Dechesne
2015-09-25 10:34   ` 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=56052350.9070405@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=nicolas.dechesne@linaro.org \
    --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