From: Mark Thompson <sw@jkqxz.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/4] lavu: Remove libva 1.x support
Date: Wed, 3 Apr 2024 21:18:20 +0100
Message-ID: <b0d9b0bb-94b8-40a5-bc55-18a5c3c77147@jkqxz.net> (raw)
In-Reply-To: <2723282.mvXUDI8C0e@basile.remlab.net>
On 03/04/2024 21:09, Rémi Denis-Courmont wrote:
> Le keskiviikkona 3. huhtikuuta 2024, 22.44.29 EEST Mark Thompson a écrit :
>> libva 2.0 was released in 2017 and the 2.x versions are included in all
>> supported distributions nowadays.
>> ---
>> libavutil/hwcontext_vaapi.c | 4 ----
>> 1 file changed, 4 deletions(-)
>>
>> diff --git a/libavutil/hwcontext_vaapi.c b/libavutil/hwcontext_vaapi.c
>> index 56d03aa4cd..bc82ab31e6 100644
>> --- a/libavutil/hwcontext_vaapi.c
>> +++ b/libavutil/hwcontext_vaapi.c
>> @@ -1637,7 +1637,6 @@ static void vaapi_device_free(AVHWDeviceContext *ctx)
>> av_freep(&priv);
>> }
>>
>> -#if CONFIG_VAAPI_1
>
> IMO, it wouldn't hurt to clarify in the change description that CONFIG_VAAPI_1
> actually corresponded to libva 2.x. No objections to the code changes though.
Fair, the library major version being the API major version plus one is a slightly bizarre feature. I've added some words to that effect locally.
Thanks,
- Mark
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2024-04-03 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 19:44 Mark Thompson
2024-04-03 19:45 ` [FFmpeg-devel] [PATCH 2/4] lavc: " Mark Thompson
2024-04-03 19:45 ` [FFmpeg-devel] [PATCH 3/4] lavfi: " Mark Thompson
2024-04-03 19:46 ` [FFmpeg-devel] [PATCH 4/4] configure: " Mark Thompson
2024-04-03 20:09 ` [FFmpeg-devel] [PATCH 1/4] lavu: " Rémi Denis-Courmont
2024-04-03 20:18 ` Mark Thompson [this message]
2024-04-03 21:29 ` Michael Niedermayer
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=b0d9b0bb-94b8-40a5-bc55-18a5c3c77147@jkqxz.net \
--to=sw@jkqxz.net \
--cc=ffmpeg-devel@ffmpeg.org \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git