On Wed, Sep 28, 2022 at 4:30 PM Nicolas Chauvet <kwizart(a)gmail.com> wrote:
> Le mar. 27 sept. 2022 à 20:57, David Airlie <airlied(a)redhat.com> a écrit :
> > On Wed, Sep 28, 2022 at 4:02 AM Frantisek Zatloukal <fzatlouk(a)redhat.com>
> > >
> > > Hi,
> > >
> > > since this mesa change (
) in F37 and rawhide, the mesa package lost support for vaapi accelerated encoding and
decoding of h264, h265 and decoding of vc1 (
> > >
> > > It seems like a big regression from F36 for users with GPUs with open
source drivers (mainly AMD, maybe nVidia/other non x86...), that affects common use-cases
of Fedora Workstation, like watching videos, in-house game streaming, attending online
meetings and many more.
> > This was an oversight being enabled prior to this, and I think we have
> > to remove it from older Fedora as well. Fedora cannot ship anything
> > that causes the OS to provide an API which exposes patent algorithms.
> > The patent licensing around H264/H265 is such that providing this
> > could leave Red Hat and other Fedora distributors exposed to legal
> > problems.
> > Dave.
> > > I'd like to ask:
> > > - Can somebody elaborate on reasons to change something that was working
in Fedora for some time already?
> > > - Is there any short/mid/long term plan to improve the situation?
> > > - Would it be possible to provide vaapi support at least as an rpmfusion
addon to alleviate the fallout in the short term?
> > The last might be possible, but I'm not sure how to go about it.
> At least I've asked in https://bugzilla.redhat.com/show_bug.cgi?id=2123998#c8
> That the fedora mesa package completely drops the vaapi backend, so a
> complementary package can just drop the missing files instead of
> rebuilding a whole mesa package.
> It would assume the fedora mesa package to have everything needed in
> order to cope with vaapi backend enabled in the core libraries and
> that the vaapi backend only provide the implementation.
Please take a look at the rawhide changes I just pushed. This should
split things out sufficiently.