From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avdevice/v4l2: add limited support for multiplanar API
Date: Thu, 27 Jun 2024 18:05:50 +0200
Message-ID: <171950435062.21847.6032165142014342003@lain.khirnov.net> (raw)
In-Reply-To: <CALweWgD2iuG+Yk-y1djyeyH4yTjj6uFaSfjiak7Z5Wu0=vsYPQ@mail.gmail.com>
Quoting Ramiro Polla (2024-06-27 16:13:24)
> On Tue, Jun 25, 2024 at 1:56 PM Ramiro Polla <ramiro.polla@gmail.com> wrote:
> > On Tue, Jun 25, 2024 at 11:19 AM Anton Khirnov <anton@khirnov.net> wrote:
> > > Quoting Ramiro Polla (2024-06-20 17:40:39)
> > > > This commit adds support for V4L2's multiplanar API, but only when the
> > > > number of planes is 1.
> > > >
> > > > Adding full support for the multiplanar API would require a device that
> > > > actually uses more than 1 plane, which I have not found yet.
> > >
> > > Out of curiosity, what's the point of a multiplanar API when the plane
> > > count is always one?
> >
> > Good question, and I wish I knew the answer. Some SBCs are providing
> > HDMI input through v4l2, and they decided to use the multiplanar API,
> > even though the count is always one.
> >
> > I couldn't find many examples on how to use this API correctly, with a
> > couple of implementations being buggy to a point where they will only
> > work when the count is one.
> >
> > I wish I could find a device that uses the multiplanar API and
> > actually provides more than one buffer so that I could properly test,
> > but by looking at the kernel source code I couldn't find a device that
> > I could easily obtain yet.
>
> Is anyone fundamentally opposed to this approach to implement limited
> support for multiplanar API? I figure it could still be useful even
> when full multiplanar API support is implemented, because multiple
> memory buffers per packet will likely mean memcpy()s, which can be
> avoided if the plane count is one.
Ideally this should be turned into a lavfi source, then multiple planes
can be exported individually.
(this is not an objection to this patch)
--
Anton Khirnov
_______________________________________________
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".
next prev parent reply other threads:[~2024-06-27 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 15:40 Ramiro Polla
2024-06-25 9:19 ` Anton Khirnov
2024-06-25 11:56 ` Ramiro Polla
2024-06-27 14:13 ` Ramiro Polla
2024-06-27 16:05 ` Anton Khirnov [this message]
2024-06-28 11:47 ` Ramiro Polla
2024-07-01 14:15 ` Anton Khirnov
2024-06-28 12:54 ` Ramiro Polla
2024-07-01 17:38 ` Ramiro Polla
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=171950435062.21847.6032165142014342003@lain.khirnov.net \
--to=anton@khirnov.net \
--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