From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/4] lavc/mpeg*: drop the XvMC hwaccel code
Date: Tue, 08 Feb 2022 10:36:53 +0100
Message-ID: <164431301321.19727.453011583235613178@lain.red.khirnov.net> (raw)
In-Reply-To: =?utf-8?q?=3CDM8P223MB03652A19235F0878A58FEC2DBA2C9=40DM8P223MB?= =?utf-8?q?0365=2ENAMP223=2EPROD=2EOUTLOOK=2ECOM=3E?=
Quoting Soft Works (2022-02-07 03:18:54)
> I sometimes wonder whether there exists a single API user who
> really understands this (very special) kind of logic and
> would make decisions based on that understanding.
>
> When it's not even fully understood internally, how should it
> be understood externally?
The rule for API users is simple: you are not allowed to assume a
specific component (like a decoder, demuxer or hwaccel) will be
available at runtime*. You are supposed to check for it using the APIs
provided for this purpose. In this case, AV_PIX_FMT_XVMC will just stop
being offered in get_format().
Not to mention that I very much doubt there are any users of xvmc left,
besides the original mplayer.
* unless you are running with a very specific verified build, in which
case a removal like this should be caught at the build stage
--
Anton Khirnov
_______________________________________________
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:[~2022-02-08 9:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 10:02 Anton Khirnov
2022-02-01 10:02 ` [FFmpeg-devel] [PATCH 2/4] lavc/xvmc.h: mark the header as deprecated Anton Khirnov
2022-02-01 10:02 ` [FFmpeg-devel] [PATCH 3/4] lavu/pixfmt: deprecate AV_PIX_FMT_XVMC Anton Khirnov
2022-02-01 10:02 ` [FFmpeg-devel] [PATCH 4/4] lavc: deprecate FF_IDCT_NONE Anton Khirnov
2022-02-01 11:16 ` Lynne
2022-02-01 11:32 ` James Almer
2022-02-07 1:46 ` [FFmpeg-devel] [PATCH 1/4] lavc/mpeg*: drop the XvMC hwaccel code Andreas Rheinhardt
2022-02-07 1:53 ` James Almer
2022-02-07 2:18 ` Soft Works
2022-02-08 9:36 ` Anton Khirnov [this message]
2022-02-08 21:34 ` Soft Works
2022-02-09 5:49 ` Anton Khirnov
2022-02-09 6:19 ` Soft Works
2022-02-09 6:38 ` Anton Khirnov
2022-02-08 9:37 ` Anton Khirnov
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=164431301321.19727.453011583235613178@lain.red.khirnov.net \
--to=anton@khirnov.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