Bug#1016687: Clarification Needed
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 somewhere else (gpu firmware or other blobs). > > vmjl > Yes, after more research, I agree with this, and for more background, see: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15258 If Debian doesn't ship the firmware, there is no issue. Please enable the codec support as Debian/mesa has been doing this by default up until the option was created.
Bug#1016687: Clarification Needed
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 retitled. It doesn't just affect VA-API > > encoding. It affects VA-API/VDPAU/Vulkan decoding and encoding of the > > codecs in question. > > > > Thank you > > > > I don't think this can be enabled, since Debian does not allow distributing > software encumbered by patents: > > https://www.debian.org/legal/patent 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 somewhere else (gpu firmware or other blobs). vmjl > > > > -- > t > > -- > To unsubscribe, send mail to 1016687-unsubscr...@bugs.debian.org. >
Bug#1016687: Clarification Needed
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/VDPAU/Vulkan decoding and encoding of the codecs in question. Thank you I don't think this can be enabled, since Debian does not allow distributing software encumbered by patents: https://www.debian.org/legal/patent -- t
Bug#1016687: Clarification Needed
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 codecs in question. Thank you
Bug#1016687:
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 support for. Distros might want to consult their legal department before enabling these. This is used for all video APIs (vaapi, vdpau, vulkan). Non-patent encumbered codecs will be enabled by default.')
