From: Elie Roudninski <xademax@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v2 0/2] Add common V4L2 request API code
Date: Wed, 13 Apr 2022 12:12:52 +0200
Message-ID: <CAJJ5kav4QBdrSZ1p5Bz=44--bEXr+a2Qg7hUU4rERNTiX5G6mQ@mail.gmail.com> (raw)
In-Reply-To: <20220412155316.22417-1-xademax@gmail.com>
Please disregard this patch series.
Since I sent those yesterday I have been contacted by the original
authors and was told that those are outdated.
Both LibreELEC and RPi devs are working on a different version of the
code that would need to be consolidated first before it can go
upstream.
Sorry for the noise.
Best regards,
Le mar. 12 avr. 2022 à 17:53, <xademax@gmail.com> a écrit :
>
> From: Elie ROUDNINSKI <xademax@gmail.com>
>
> This is the second iteration of https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=2898
> but only covering the common V4L2 request API code without the support for h264 codec.
>
> Changes in v2:
> * Addressed some styling comments
> * Removed libudev dependency
> * Device probing has been refactored
>
> This code (in one version or another) has been widely used by various projects
> like LibreELEC[1] for several years already.
> The uAPI has been stable for several kernel versions too and as of linux5.17,
> the following codecs are available:
> * mpeg2
> * h264
> * vp9
>
> HEVC is in the process of being stabilized too[2].
>
> I have tried to contact the original author of the code but I haven't got an answer
> so far so I have kept them as commit author but added myself as co-author since
> I have made substantial modifications to it. Happy to change this either way.
>
> It's my first contribution to FFmpeg, so I hope to have done everything right.
> Additionally, I must confess that I am not an expert of the V4L2 request APIs but
> since I was frustrated of not being able to use standard FFmpeg on my ARM boards
> to get hardware decoding working, I figured I might just try to give it a go.
> There are several comments in the original patch series that I won't have an answer
> for but I hope that won't be a blocker. That's also why the v4l2-request configure
> option has been marked as experimental.
>
> [1] https://github.com/LibreELEC/LibreELEC.tv/tree/master/packages/multimedia/ffmpeg/patches/v4l2-request
> [2] https://patchwork.kernel.org/project/linux-media/list/?series=630077
>
>
> Jonas Karlman (2):
> avutil/buffer: add av_buffer_pool_flush()
> avcodec: add common V4L2 request API code
>
> configure | 7 +
> doc/APIchanges | 3 +
> libavcodec/Makefile | 3 +-
> libavcodec/hwconfig.h | 2 +
> libavcodec/v4l2_buffers.c | 8 +-
> libavcodec/v4l2_context.c | 80 ++--
> libavcodec/v4l2_context.h | 5 +-
> libavcodec/v4l2_device.c | 229 ++++++++++
> libavcodec/v4l2_device.h | 60 +++
> libavcodec/v4l2_m2m.c | 119 ++---
> libavcodec/v4l2_m2m.h | 4 +-
> libavcodec/v4l2_m2m_dec.c | 10 +-
> libavcodec/v4l2_m2m_enc.c | 8 +-
> libavcodec/v4l2_request.c | 892 ++++++++++++++++++++++++++++++++++++++
> libavcodec/v4l2_request.h | 87 ++++
> libavutil/buffer.c | 7 +
> libavutil/buffer.h | 5 +
> libavutil/version.h | 4 +-
> 18 files changed, 1399 insertions(+), 134 deletions(-)
> create mode 100644 libavcodec/v4l2_device.c
> create mode 100644 libavcodec/v4l2_device.h
> create mode 100644 libavcodec/v4l2_request.c
> create mode 100644 libavcodec/v4l2_request.h
>
> --
> 2.35.1
>
_______________________________________________
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".
prev parent reply other threads:[~2022-04-13 10:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 15:53 xademax
2022-04-12 15:53 ` [FFmpeg-devel] [PATCH v2 1/2] avutil/buffer: add av_buffer_pool_flush() xademax
2022-04-12 15:53 ` [FFmpeg-devel] [PATCH v2 2/2] avcodec: add common V4L2 request API code xademax
2022-04-13 10:12 ` Elie Roudninski [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='CAJJ5kav4QBdrSZ1p5Bz=44--bEXr+a2Qg7hUU4rERNTiX5G6mQ@mail.gmail.com' \
--to=xademax@gmail.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