Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Ronald S. Bultje" <rsbultje-at-gmail.com@ffmpeg.org>
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: Tue, 8 Jul 2025 09:33:40 -0400
Message-ID: <CAEEMt2kSnvvfFaK9X7Vd4oT-Hp9m9t0hYiuM-RYCpWMrJ5fkFA@mail.gmail.com> (raw)
In-Reply-To: <YT2PR01MB66732FB578C7271C0AD72BB1FE4EA@YT2PR01MB6673.CANPRD01.PROD.OUTLOOK.COM>

Hi,

On Mon, Jul 7, 2025 at 9:00 PM Desmond Liu <desmond.liu@netint.ca> wrote:

>   *   As far as I know, these cards/units are not available to the general
> public at all.
>
> The cards are available to the general public. See
> https://netint.com/contact-us and send a message to sales@netint.com
> <mailto:sales@netint.com>. There is no minimum order nor any NDA that
> needs to be signed.


We previously had a similar debate regarding realmedia (search for "Codec
wrapper for librv11 and RMHD muxer/demuxer").

The debate comes down to this:
- it's clear that for the company, there's a huge advantage in patches
being upstream. For example, upstream does maintenance/upkeep for free.
- it's not clear whether there is any benefit to the community / project in
this patch being upstream. For example, how do we test this code in fate?

The fact that something is for sale does not mean it's a general benefit to
the FFmpeg developer or user community.

Ronald
_______________________________________________
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".

  reply	other threads:[~2025-07-08 13:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  0:59 Desmond Liu
2025-07-08 13:33 ` Ronald S. Bultje [this message]
2025-07-08 20:41   ` Marton Balint
2025-07-09  2:11   ` Desmond Liu
2025-07-08 19:37 ` Kieran Kunhya via ffmpeg-devel
  -- strict thread matches above, loose matches on Subject: below --
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=CAEEMt2kSnvvfFaK9X7Vd4oT-Hp9m9t0hYiuM-RYCpWMrJ5fkFA@mail.gmail.com \
    --to=rsbultje-at-gmail.com@ffmpeg.org \
    --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