Bug#1016687: Clarification Needed

2022-08-17 Thread Dan Letzeisen
On Tue, 16 Aug 2022 14:06:56 +0200 Victor Jaquez wrote: > > In that case intel-media-va-driver and i965-va-driver wouldn't be > distributed either. > > If I understand correctly, they are distributed because they don't > contain the codec logic, only the data structures. The logic is > defined so

Bug#1016687: Clarification Needed

2022-08-16 Thread Victor Jaquez
On Tue, 16 Aug 2022 at 14:44, Timo Aaltonen wrote: > Dan Letzeisen kirjoitti 15.8.2022 klo 0.10: > > I realize this is a tricky situation with dfsg, but is there any intent > > to fix this bug at Debian distro level or should we look at building our > > own mesa? > > > > Also, the bug should be re

Bug#1016687: Clarification Needed

2022-08-16 Thread Timo Aaltonen
Dan Letzeisen kirjoitti 15.8.2022 klo 0.10: I realize this is a tricky situation with dfsg, but is there any intent to fix this bug at Debian distro level or should we look at building our own mesa? Also, the bug should be retitled. It doesn't just affect VA-API encoding. It affects VA-API/VD

Bug#1016687: Clarification Needed

2022-08-14 Thread Dan Letzeisen
I realize this is a tricky situation with dfsg, but is there any intent to fix this bug at Debian distro level or should we look at building our own mesa? Also, the bug should be retitled. It doesn't just affect VA-API encoding. It affects VA-API/VDPAU/Vulkan decoding and encoding of the code

Bug#1016687:

2022-08-05 Thread Florian Zwoch
Looks like in new Mesa you will have to explicitly enable codec support for the ones that are patent encumbered: option( 'video-codecs', type : 'array', value : [], choices: [ 'vc1dec', 'h264dec', 'h264enc', 'h265dec', 'h265enc' ], description : 'List of patent encumbered codecs to build sup