From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/libva: remove optional mesa3d support
Date: Wed, 10 Apr 2019 19:43:22 +0200 [thread overview]
Message-ID: <qim1ofxi21.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20190410191307.1681df76@windsurf.home
Am Wed, 10 Apr 2019 19:13:07 +0200 schrieb Thomas Petazzoni:
> 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 ?
Hi Thomas,
first I like to mention that I do not have any AMD hardware in use with
buildroot, I am just following the development of Libreelec:
https://github.com/xbmc/xbmc/pull/13333
https://github.com/LibreELEC/LibreELEC.tv/pull/2403
The motivation for the Kodi patch was: "Hardware decoding with AMD GPUs
is only supported with this new method"
Because I think this will improve user experience with AMD hardware I
sent these patches.
Regards, Bernd
prev parent reply other threads:[~2019-04-10 17:43 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 ` [Buildroot] [PATCH 1/2] package/libva: remove optional mesa3d support Thomas Petazzoni
2019-04-10 17:43 ` Bernd Kuhls [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=qim1ofxi21.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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.