Bug 2148680 - [Rebase] Rebase libva to 2.16.0 or higher for RHEL 9.3
Summary: [Rebase] Rebase libva to 2.16.0 or higher for RHEL 9.3
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libva
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jiri Kucera
QA Contact: Tomas Pelka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-27 02:51 UTC by Neal Gompa
Modified: 2023-07-24 12:05 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Component Upgrade
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/rpms libva merge_requests 4 0 None opened Rebase to 2.16.0 2022-11-27 02:53:45 UTC
Red Hat Issue Tracker RHELPLAN-140545 0 None None None 2022-11-27 03:04:26 UTC

Description Neal Gompa 2022-11-27 02:51:04 UTC 
Description of problem:
Newer versions of libva enable support for hardware accelerated encoding of AV1, which is required for a number of professional use-cases around creating content. As hardware has become available through 2022 for hardware-accelerated AV1 encoding, RHEL should have a newer libva to take advantage of this capability.
Comment 1 Neal Gompa 2022-11-27 02:53:45 UTC 
Merge request proposed: https://gitlab.com/redhat/centos-stream/rpms/libva/-/merge_requests/4
Comment 2 Neal Gompa 2023-02-03 17:55:41 UTC 
Hey Niels, can you help unstick this please?

Also, I just bumped this MR to 2.17.0 since it apparently came out a while ago and is in Fedora too...
Comment 5 Niels De Graef 2023-03-13 09:59:36 UTC 
Removing needinfo on me. The associated team said they will try to take a look at getting this in for 9.3, the ball is in their court now :-)
Comment 7 Neal Gompa 2023-07-24 12:04:57 UTC 
Friendly ping?

I've bumped the MR to libva 2.19.0 since that's been around for a while in Fedora now...
Note You need to log in before you can comment on or make changes to this bug.