From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: zboszor@pr.hu,
"Bartłomiej Burdukiewicz" <bartlomiej.burdukiewicz@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][PATCH] libva: Removed virtual/mesa dependency
Date: Thu, 07 May 2020 12:48:56 +0100 [thread overview]
Message-ID: <610a380ebc8ef2638a8d13c8d3a84b3059bcf8aa.camel@linuxfoundation.org> (raw)
In-Reply-To: <44fb22eb-a3ea-15cb-f93e-c0ff4503705b@pr.hu>
On Wed, 2020-05-06 at 14:41 +0200, Zoltan Boszormenyi via
lists.openembedded.org wrote:
> 2020. 04. 24. 17:01 keltezéssel, Bartłomiej Burdukiewicz írta:
> > Mesa can be compiled with libva support, in order to avoid
> > recursive
> > dependency between mesa and libva, virtual/mesa must be removed
> > from libva recipe.
>
> This is why this patch series was created, to break the
> circular dependency in a clean way:
> https://patchwork.openembedded.org/series/22976/#
>
> The libva-initial recipe was introduced that doesn't need
> mesa, then mesa can be built with vaapi state tracker enabled,
> finally libva can be built with dependency on mesa so its
> GLX support is enabled.
>
> What happened to it?
I think it came in late during the release and was a bit too risky to
be taken at the time. It think it is a good solution to the problem,
would you be able to rebase the patches and we can queue them for
testing? Its a much better time now to merge a change like that.
Cheers,
Richard
next prev parent reply other threads:[~2020-05-07 11:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 15:01 [meta-oe][PATCH] libva: Removed virtual/mesa dependency bartlomiej.burdukiewicz
2020-04-25 4:46 ` [OE-core] " Khem Raj
2020-04-25 19:38 ` Bartłomiej Burdukiewicz
2020-04-25 23:03 ` [OE-core] " Fred Baksik
2020-04-26 4:23 ` Anuj Mittal
2020-04-27 23:09 ` Bartłomiej Burdukiewicz
2020-04-28 8:47 ` Richard Purdie
2020-04-29 11:50 ` Bartłomiej Burdukiewicz
2020-05-06 12:41 ` Zoltan Boszormenyi
2020-05-07 11:25 ` Bartłomiej Burdukiewicz
2020-05-07 11:48 ` Richard Purdie [this message]
2020-05-07 12:47 ` Zoltan Boszormenyi
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=610a380ebc8ef2638a8d13c8d3a84b3059bcf8aa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bartlomiej.burdukiewicz@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=zboszor@pr.hu \
/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