From: Tom Zanussi <tom.zanussi@intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: yocto@yoctoproject.org, dvhart@linux.intel.com
Subject: Re: [PATCH 1/1] meta-intel: make video acceleration choice dependent on LICENSE_FLAGS
Date: Fri, 14 Sep 2012 16:25:06 -0500 [thread overview]
Message-ID: <1347657906.6185.17.camel@empanada> (raw)
In-Reply-To: <CAJTo0LbgWdoX8GnMsKYa-y176X1YiTEd7Ucw7CNLLi6OBqaB2g@mail.gmail.com>
On Fri, 2012-09-14 at 21:51 +0100, Burton, Ross wrote:
> On 14 September 2012 20:27, <tom.zanussi@intel.com> wrote:
> > The gst-ffmpeg recipe in oe-core had LICENSE_FLAGS added to make it
> > "commercial", so to avoid build errors the BSPs that use it (via the
> > gst-va-intel VA_FEATURE) should only include it if the user has added
> > "commercial" to LICENSE_FLAGS_WHITELIST when building.
>
> It's entirely possible to use gst-vaapi without commercial plugins,
> the problem is the (mysterious to me) dependency on gst-ffmpeg.
>
From the gstreamer-vaapi README:
"vaapidecoder currently relies on FFmpeg"
> How about making gst-ffmpeg a recommends instead of rdepends, so that
> if it's blacklisted due to license flags there isn't a build failure.
I can try that and see what happens.
> gst-vaapi doesn't have license issues to making it disappear when
> avoiding commercial licenses doesn't make sense.
>
> (I'd also like to understand why gst-ffmpeg is a rdepends at all)
>
The only avenue I was able to find (that worked, an important point) to
get gstreamer to use video acceleration was via ffmpeg (via gst-ffmpeg,
needed for making ffmpeg available to the gstreamer pipeline) with the
--with-vaapi option.
Believe me, I went through a bunch of iterations of different versions
and combinations of all these components before hitting on something
that didn't always segfault and gave more than 1/2 a frame a second
(literally), and that was after using code that supposedly worked for an
ELC demo...
Anyway, it would be nice if someone who had a better understanding of
this 'stack' could suggest better ways of doing things - at this point
it works for 3 different video acceleration implementations (emgd, pvr
and standard intel va) and I'm not looking forward to going through that
exercise again - for now I'll just be trying to fix the build problems
introduced by the new licensing restrictions.
Tom
> Ross
next prev parent reply other threads:[~2012-09-14 21:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 19:27 [PATCH 0/1] meta-intel: BSP updates for gst-ffmpeg LICENSE_FLAGS change tom.zanussi
2012-09-14 19:27 ` [PATCH 1/1] meta-intel: make video acceleration choice dependent on LICENSE_FLAGS tom.zanussi
2012-09-14 20:51 ` Burton, Ross
2012-09-14 21:25 ` Tom Zanussi [this message]
2012-09-14 21:39 ` Burton, Ross
2012-09-14 21:52 ` Tom Zanussi
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=1347657906.6185.17.camel@empanada \
--to=tom.zanussi@intel.com \
--cc=dvhart@linux.intel.com \
--cc=ross.burton@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.