From: Desmond Liu <desmond.liu@netint.ca>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/3] libavcodec: add NETINT Quadra HW decoders & encoders
Date: Fri, 11 Jul 2025 02:03:31 +0000
Message-ID: <YT2PR01MB6673E4A765A279A86D9BCC09FE48A@YT2PR01MB6673.CANPRD01.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <5569e4b0-8101-4e6e-a52b-fafea5de510d@rothenpieler.org>
Hi Timo,
> I'm very much in favour of adding support. Assuming it is then also
> properly maintained and not just "dumped" on us.
> Of course we can't reasonably add support for every single niche bit of
> hardware, but this seems mature and adopted enough to me to warrant it.
Thanks. We don't really plan on "dumping" these changes into FFmpeg. We
want to add FATE testing to ensure upstream FFmpeg commits continue to
work with our hardware. We plan on contributing fixes to FFmpeg as
necessary.
Internally, we will run more extensive testing against the master branch
nightly on our hardware. We will actively testing release candidates.
We will likely have to add ourselves as a maintainer responsible for
our hardware.
Desmond
_______________________________________________
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:[~2025-07-11 2:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 0:59 Desmond Liu
2025-07-08 13:33 ` Ronald S. Bultje
2025-07-08 20:41 ` Marton Balint
2025-07-09 2:11 ` Desmond Liu
2025-07-09 12:04 ` Timo Rothenpieler
2025-07-11 2:03 ` Desmond Liu [this message]
2025-07-08 19:37 ` Kieran Kunhya via ffmpeg-devel
-- strict thread matches above, loose matches on Subject: below --
2025-07-09 17:41 Desmond Liu
2025-07-07 21:21 Desmond Liu
2025-07-02 8:11 Steven Zhou
2025-07-02 14:33 ` Derek Buitenhuis
2025-07-02 16:33 ` Steven Zhou
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=YT2PR01MB6673E4A765A279A86D9BCC09FE48A@YT2PR01MB6673.CANPRD01.PROD.OUTLOOK.COM \
--to=desmond.liu@netint.ca \
--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