I would be very SAD if this change lands on my computer. While instead
of arguing with some legal puzzles, I think those parts can be provided
by seperate package (and maybe packaged in rpmfusion?) like intel-
media-driver.
Is there any build-to-build ABI match requirement between the VAAPI
implementation and mesa itself?
在 2022-09-27星期二的 20:01 +0200,Frantisek Zatloukal写道:
Hi,
since this mesa change
( https://src.fedoraproject.org/rpms/mesa/c/94ef544b3f2125912dfbff4c6
ef373fe49806b52?branch=rawhide ) in F37 and rawhide, the mesa package
lost support for vaapi accelerated encoding and decoding of h264,
h265 and decoding of vc1
( https://bugzilla.redhat.com/show_bug.cgi?id=2123998 ).
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.
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?
Thanks!
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue