From: Steven Xiao via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: Steven Xiao <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] avfilter/dnn: fix XPU initialization API call in torch backend (PR #21664)
Date: Fri, 06 Feb 2026 18:08:01 -0000
Message-ID: <177040128177.25.13087803173203680565@4457048688e7> (raw)
PR #21664 opened by Steven Xiao (younengxiao)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21664
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21664.patch
The correct initialization API for XPU is init(), not initXPU().
>From 720d5dc946217deffa62371ff1049a88e5744da1 Mon Sep 17 00:00:00 2001
From: stevxiao <steven.xiao@amd.com>
Date: Fri, 6 Feb 2026 13:01:26 -0500
Subject: [PATCH] avfilter/dnn: fix XPU initialization API call in torch
backend
The correct initialization API for XPU is init(), not initXPU().
---
libavfilter/dnn/dnn_backend_torch.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavfilter/dnn/dnn_backend_torch.cpp b/libavfilter/dnn/dnn_backend_torch.cpp
index 33809bf983..f5a92d2c58 100644
--- a/libavfilter/dnn/dnn_backend_torch.cpp
+++ b/libavfilter/dnn/dnn_backend_torch.cpp
@@ -507,7 +507,7 @@ static DNNModel *dnn_load_model_th(DnnContext *ctx, DNNFunctionType func_type, A
av_log(ctx, AV_LOG_ERROR, "No XPU device found\n");
goto fail;
}
- at::detail::getXPUHooks().initXPU();
+ at::detail::getXPUHooks().init();
} else if (!device.is_cpu()) {
av_log(ctx, AV_LOG_ERROR, "Not supported device:\"%s\"\n", device_name);
goto fail;
--
2.52.0
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2026-02-06 18:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=177040128177.25.13087803173203680565@4457048688e7 \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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