All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: mesa-24.1.4 incompatibility with unpatched ffmpeg
Date: Sat, 20 Jul 2024 04:26:24 +0100	[thread overview]
Message-ID: <87bk2syc9r.fsf@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 979 bytes --]

Hi!

For those shipping mesa-24.1.4, please check whether your copy of ffmpeg
has the patches at https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29400#note_2432971
applied, i.e.:

* lavc/vaapi_decode: Make it possible to send multiple slice params buffers
** https://github.com/FFmpeg/FFmpeg/commit/fe9d889dcd79ea18d4dfaa39df4ddbd4c8c3b15c
* lavc/vaapi_av1: Avoid sending the same slice buffer multiple times
** https://github.com/FFmpeg/FFmpeg/commit/d2d911eb9a2fc6eb8d86b3ae025a56c1a2692fba

At a glance, I don't _think_ those patches are shipped in any release or
backported on any of the ffmpeg branches yet, but please don't take my
word for it as I only looked briefly and will check properly
later. Apologies to ffmpeg if I'm wrong.

Firefox's bundled ffmpeg is also affected, see below.

Other references:
* https://bugs.gentoo.org/936310
* https://gitlab.freedesktop.org/mesa/mesa/-/issues/11533
* https://phabricator.services.mozilla.com/D216919

thanks,
sam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

             reply	other threads:[~2024-07-20  3:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-20  3:26 Sam James [this message]
2024-07-20  3:59 ` mesa-24.1.4 incompatibility with unpatched ffmpeg Neal Gompa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bk2syc9r.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=distributions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.