From: Mark Thompson <sw@jkqxz.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v3 1/4] lavu: Remove libva 1.x support
Date: Sun, 28 Apr 2024 15:21:06 +0100
Message-ID: <31235b42-2cb7-4a42-8f4a-06901620ddbe@jkqxz.net> (raw)
In-Reply-To: <067424dc4db4dd78267d45a020739d94a7a0e968.camel@intel.com>
On 24/04/2024 15:06, Xiang, Haihao wrote:
> On Ma, 2024-04-22 at 22:41 +0100, Mark Thompson wrote:
>> libva 2.0 was released in 2017 and the 2.x versions are included in all
>> supported distributions nowadays.
>> ---
>> Rebased.
>>
>> I think we can also drop the other quirks? They are for the proprietary media
>> SDK driver (which I think is dead?) and the VDPAU wrapper (which I don't think
>> was ever updated for libva 2?).
>
> Agree, please drop these quirks in a new patch.
Sure.
> BTW I think we should require VA-API 1.x firstly, otherwise if someone has VA-
> API 0.x, he/she will get errors when building this commit.
I was intending to squash but had them split for review, though as you say they can stay split with more careful ordering - I will do this.
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".
prev parent reply other threads:[~2024-04-28 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 21:41 Mark Thompson
2024-04-22 21:42 ` [FFmpeg-devel] [PATCH v3 2/4] lavc: " Mark Thompson
2024-04-22 21:43 ` [FFmpeg-devel] [PATCH v3 3/4] lavfi: " Mark Thompson
2024-04-22 21:44 ` [FFmpeg-devel] [PATCH v3 4/4] configure: " Mark Thompson
2024-04-24 14:06 ` [FFmpeg-devel] [PATCH v3 1/4] lavu: " Xiang, Haihao
2024-04-28 14:21 ` Mark Thompson [this message]
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=31235b42-2cb7-4a42-8f4a-06901620ddbe@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