Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Jianfeng Zheng <ggjogh@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: haihao.xiang@intel.com, Liu Steven <lq@chinaffmpeg.org>,
	"jianfeng.zheng" <jianfeng.zheng@mthreads.com>,
	carl.zhang@intel.com
Subject: Re: [FFmpeg-devel] [PATCH v1 2/2] vaapi: add vaapi_avs2 support
Date: Mon, 22 Jan 2024 20:32:21 +0800
Message-ID: <CAFWZL8ry-nk_zdmLOqq=537u-K7HFrCv-UoAtpvRVSfdAqbyTw@mail.gmail.com> (raw)
In-Reply-To: <tencent_71F04F8455682709B883964DCD73A029CD07@qq.com>

Zhao Zhili <quinkblack@foxmail.com> 于2024年1月22日周一 20:02写道:
>
>
>
> > On Jan 22, 2024, at 08:06, Liu Steven <lq@chinaffmpeg.org> wrote:
> >
> >
> >
> >> On Jan 21, 2024, at 22:47, Jianfeng Zheng <ggjogh@gmail.com> wrote:
> >>
> >> Zhao Zhili <quinkblack@foxmail.com> 于2024年1月20日周六 12:22写道:
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of jianfeng.zheng
> >>>> Sent: 2024年1月19日 23:53
> >>>> To: ffmpeg-devel@ffmpeg.org
> >>>> Cc: jianfeng.zheng <jianfeng.zheng@mthreads.com>
> >>>> Subject: [FFmpeg-devel] [PATCH v1 2/2] vaapi: add vaapi_avs2 support
> >>>>
> >>>> see https://github.com/intel/libva/pull/738
> >>>>
> >>>> [Moore Threads](https://www.mthreads.com) (short for Mthreads) is a
> >>>> Chinese GPU manufacturer. All our products, like MTTS70/MTTS80/.. ,
> >>>> support AVS2 8bit/10bit HW decoding at max 8k resolution.
> >>>>
> >>>> Signed-off-by: jianfeng.zheng <jianfeng.zheng@mthreads.com>
> >>>> ---
> >>>> configure                    |   7 +
> >>>> libavcodec/Makefile          |   2 +
> >>>> libavcodec/allcodecs.c       |   1 +
> >>>> libavcodec/avs2.c            | 345 ++++++++++++++-
> >>>> libavcodec/avs2.h            | 460 +++++++++++++++++++-
> >>>> libavcodec/avs2_parser.c     |   5 +-
> >>>> libavcodec/avs2dec.c         | 569 +++++++++++++++++++++++++
> >>>> libavcodec/avs2dec.h         |  48 +++
> >>>> libavcodec/avs2dec_headers.c | 787 +++++++++++++++++++++++++++++++++++
> >>>> libavcodec/codec_desc.c      |   5 +-
> >>>> libavcodec/defs.h            |   4 +
> >>>> libavcodec/hwaccels.h        |   1 +
> >>>> libavcodec/libdavs2.c        |   2 +-
> >>>> libavcodec/profiles.c        |   6 +
> >>>> libavcodec/profiles.h        |   1 +
> >>>> libavcodec/vaapi_avs2.c      | 227 ++++++++++
> >>>> libavcodec/vaapi_decode.c    |   5 +
> >>>> libavformat/matroska.c       |   1 +
> >>>> libavformat/mpeg.h           |   1 +
> >>>> 19 files changed, 2450 insertions(+), 27 deletions(-)
> >>>> create mode 100644 libavcodec/avs2dec.c
> >>>> create mode 100644 libavcodec/avs2dec.h
> >>>> create mode 100644 libavcodec/avs2dec_headers.c
> >>>> create mode 100644 libavcodec/vaapi_avs2.c
> >>>>
> >>>
> >>> Please split the patch properly. It's hard to review in a single chunk, and it can't be tested
> >>> without the hardware.
> >>
> >> As a new player in the GPU market, we have always attached great importance
> >> to the participation of the open source community. And willing to feed back our
> >> new features to the field of video hardware acceleration.
> >>
> >> As a pioneer, these new features may only be supported by our hardware
> >> at current
> >> time. We are willing to provide some market selling devices for free
> >> to community
> >> accredited contributors for testing related functions.
> > I accredited Zhili Zhao, but i cannot sure Zhili Zhao have interest in the GPU card and not sure he has a computer can insert a PCI GPU card:D
>
> I have done a little work on AVS/AVS2/AVS3 and some hardware acceleration work.
> I have a Lenovo 7000K and Dell Precision 3640, and I’m more concerned about driver.

If you using Ubuntu driver is easy by install our all-in-one deb driver package.

Some how the problem is VAAPI-AVS/AVS2 interfaces should be accected by
Intel first. I'm wondering if Intel guys would be interest in taking
try our newest
devices like S80?

>
> >
> >>
> >>>
> >>> _______________________________________________
> >>> 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".
> >> _______________________________________________
> >> 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".
> >
> >
> > _______________________________________________
> > 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".
>
> _______________________________________________
> 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".
_______________________________________________
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-01-22 12:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19 15:53 jianfeng.zheng
2024-01-20  4:22 ` Zhao Zhili
2024-01-21 14:47   ` Jianfeng Zheng
2024-01-22  0:06     ` Liu Steven
2024-01-22 11:56       ` Zhao Zhili
2024-01-22 12:32         ` Jianfeng Zheng [this message]

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='CAFWZL8ry-nk_zdmLOqq=537u-K7HFrCv-UoAtpvRVSfdAqbyTw@mail.gmail.com' \
    --to=ggjogh@gmail.com \
    --cc=carl.zhang@intel.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=haihao.xiang@intel.com \
    --cc=jianfeng.zheng@mthreads.com \
    --cc=lq@chinaffmpeg.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