Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Brad Smith <brad-at-comstyle.com@ffmpeg.org>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>,
	Timo Rothenpieler <timo@rothenpieler.org>
Subject: Re: [FFmpeg-devel] [PATCH] configure: enable ffnvcodec, nvenc, nvdec for FreeBSD
Date: Sun, 26 May 2024 01:22:23 -0400
Message-ID: <9de3e59f-8225-49e0-9aef-c0e862e1c1bd@comstyle.com> (raw)
In-Reply-To: <a31b6003-0ca5-4176-909a-5f66cbb670ca@rothenpieler.org>

On 2024-05-19 7:24 a.m., Timo Rothenpieler wrote:
> On 19.05.2024 02:00, Brad Smith wrote:
>> configure: enable ffnvcodec, nvenc, nvdec for FreeBSD
>>
>> Signed-off-by: Brad Smith <brad@comstyle.com>
>> ---
>>   configure | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/configure b/configure
>> index b16722d83d..96b181fd21 100755
>> --- a/configure
>> +++ b/configure
>> @@ -7350,7 +7350,7 @@ fi
>>     if enabled x86; then
>>       case $target_os in
>> -        mingw32*|mingw64*|win32|win64|linux|cygwin*)
>> +        freebsd|mingw32*|mingw64*|win32|win64|linux|cygwin*)
>
> Does this actually work?
> Everything I find online indicates that the FreeBSD driver is lacking 
> support for CUDA, nvenc and most of anything compute related.


According to the commits and bug report requesting support it does 
appear to work.

The CUDA bits are not native. They're using Linux emulation for that. 
The display driver is
native.

_______________________________________________
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:[~2024-05-26  5:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19  0:00 Brad Smith
2024-05-19 11:24 ` Timo Rothenpieler
2024-05-26  5:22   ` Brad Smith [this message]
2024-05-26 11:28     ` Timo Rothenpieler

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=9de3e59f-8225-49e0-9aef-c0e862e1c1bd@comstyle.com \
    --to=brad-at-comstyle.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=timo@rothenpieler.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