From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libva: remove optional mesa3d support
Date: Wed, 10 Apr 2019 19:13:07 +0200 [thread overview]
Message-ID: <20190410191307.1681df76@windsurf.home> (raw)
In-Reply-To: <20190407171318.19852-1-bernd.kuhls@t-online.de>
Hello Bernd,
On Sun, 7 Apr 2019 19:13:17 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Kodi 18.0-Leia will support vaapi on r600 and radeonsi.
> We need libva support in mesa3d for this. To avoid the circular
> dependency we switch from using mesa3d in libva to use libva in mesa3d.
>
> This patch is the first step: disable mesa3d support in libva.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/libva/libva.mk | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
I understand the circular dependency issue, but what makes it
reasonable to drop mesa3d support in libva ? Until now, the choice was
rather the opposite: have mesa3d support in libva, and no libva support
in mesa3d. Is there a fundamental reason why one is more useful than
the other ?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-10 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 17:13 [Buildroot] [PATCH 1/2] package/libva: remove optional mesa3d support Bernd Kuhls
2019-04-07 17:13 ` [Buildroot] [PATCH 2/2] package/mesa3d: add optional support for libva Bernd Kuhls
2019-04-10 17:13 ` Thomas Petazzoni [this message]
2019-04-10 17:43 ` [Buildroot] [PATCH 1/2] package/libva: remove optional mesa3d support Bernd Kuhls
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=20190410191307.1681df76@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.