Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Wu Jianhua <toqsxw@outlook.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec: add D3D12VA hardware accelerated H264, HEVC, VP9, and AV1 decoding
Date: Tue, 11 Apr 2023 15:36:16 +0000
Message-ID: <OSZP286MB21736C00CEAAB6F27CECB33DCA9A9@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <SN6PR11MB29902C73E0B6A12F0C1AF3B8C0AC9@SN6PR11MB2990.namprd11.prod.outlook.com>

> From: Wu, Tong1<mailto:tong1.wu-at-intel.com@ffmpeg.org>
> Sent: 2023年2月28日 22:51
> To: FFmpeg development discussions and patches<mailto:ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec: add D3D12VA hardware accelerated H264, HEVC, VP9, and AV1 decoding
>
>> [PATCH v2] avcodec: add D3D12VA hardware accelerated H264, HEVC, VP9,
>> and AV1 decoding
>>
>> Patches attached.
>
>>-                    HWACCEL_D3D11VA2(h264),
>>+                               HWACCEL_D3D11VA(h264),
>
>This shouldn't be changed. It will block d3d11va h264dec.

Yes, I should not change it. I will fix it in the next patch.

Thanks.
Jianhua

>
>>+#endif
>>+#if CONFIG_H264_D3D12DEC_HWACCEL
>>+                               HWACCEL_D3D12DEC(h264),


_______________________________________________
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:[~2023-04-11 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OSZP286MB217380EBFB2351E3B8B54E25CAE99@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM>
2022-12-23 18:01 ` Wu Jianhua
2023-02-28 14:50   ` Wu, Tong1
2023-04-11 15:36     ` Wu Jianhua [this message]
2023-03-01 15:55   ` Hendrik Leppkes
2023-04-11 16:41     ` Wu Jianhua
2023-04-11 17:28       ` Hendrik Leppkes
2023-04-11 19:03         ` Wu Jianhua
2023-03-01 15:52 Anton Khirnov
2023-04-11 17:03 ` Wu Jianhua

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=OSZP286MB21736C00CEAAB6F27CECB33DCA9A9@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM \
    --to=toqsxw@outlook.com \
    --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