From: Hans Verkuil <hverkuil@xs4all.nl>
To: Ezequiel Garcia <ezequiel@collabora.com>, linux-media@vger.kernel.org
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
kernel@collabora.com,
Nicolas Dufresne <nicolas.dufresne@collabora.com>,
Tomasz Figa <tfiga@chromium.org>
Subject: Re: [PATCH v2 0/4] vicodec: a couple fixes towards spec compliancy
Date: Mon, 17 Jun 2019 14:43:55 +0200 [thread overview]
Message-ID: <879d93cc-3777-bd61-5c14-34108fc8501a@xs4all.nl> (raw)
In-Reply-To: <20181102155206.13681-1-ezequiel@collabora.com>
Hi Ezequiel,
On 11/2/18 4:52 PM, Ezequiel Garcia wrote:
> Given the stateful codec specification is still a moving target,
> it doesn't make any sense to try to comply fully with it.
>
> On the other side, we can still comply with some basic userspace
> expectations, with just a couple small changes.
>
> This series implements proper resolution changes propagation,
> and fixes the CMD_STOP so it actually works.
>
> The intention of this series is to be able to test this driver
> using already existing userspace, gstreamer in particular.
> With this changes, it's possible to construct variations of
> this pipeline:
>
> gst-launch-1.0 videotestsrc ! v4l2fwhtenc ! v4l2fwhtdec ! fakevideosink
>
> Also, as discussed in v1 feedback [1,2], I'm including pixel format
> helpers, as RFC for now. Hans, Tomasz: is this what you had in mind?
>
> [1] https://www.spinics.net/lists/linux-media/msg141912.html
> [2] https://www.spinics.net/lists/linux-media/msg142099.html
>
> v2:
> * Add more info to commit logs
> * Propagate changes on both encoders and decoders
> * Add pixel format helpers
>
> Ezequiel Garcia (4):
> media: Introduce helpers to fill pixel format structs
This one has been applied (or probably a later version) already.
> vicodec: Use pixel format helpers
This doesn't apply anymore, but it would be useful to have.
If you can rebase it, then that would be nice.
> vicodec: Propagate changes to the CAPTURE queue
> vicodec: Implement spec-compliant stop command
This two are obsolete as far as I know. The vicodec driver should handle
this correctly now. If you think otherwise, please let me know.
Regards,
Hans
>
> .../media/platform/vicodec/codec-v4l2-fwht.c | 42 ++--
> .../media/platform/vicodec/codec-v4l2-fwht.h | 3 -
> drivers/media/platform/vicodec/vicodec-core.c | 197 +++++++++---------
> drivers/media/v4l2-core/Makefile | 2 +-
> drivers/media/v4l2-core/v4l2-common.c | 66 ++++++
> drivers/media/v4l2-core/v4l2-fourcc.c | 93 +++++++++
> include/media/v4l2-common.h | 5 +
> include/media/v4l2-fourcc.h | 53 +++++
> 8 files changed, 332 insertions(+), 129 deletions(-)
> create mode 100644 drivers/media/v4l2-core/v4l2-fourcc.c
> create mode 100644 include/media/v4l2-fourcc.h
>
next prev parent reply other threads:[~2019-06-17 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 15:52 [PATCH v2 0/4] vicodec: a couple fixes towards spec compliancy Ezequiel Garcia
2018-11-02 15:52 ` [RFC v2 1/4] media: Introduce helpers to fill pixel format structs Ezequiel Garcia
2018-11-02 17:30 ` Nicolas Dufresne
2018-11-10 11:19 ` Ezequiel Garcia
2018-11-02 15:52 ` [PATCH v2 2/4] vicodec: Use pixel format helpers Ezequiel Garcia
2018-11-02 15:52 ` [PATCH v2 3/4] vicodec: Propagate changes to the CAPTURE queue Ezequiel Garcia
2018-11-02 15:52 ` [PATCH v2 4/4] vicodec: Implement spec-compliant stop command Ezequiel Garcia
2019-06-17 12:43 ` Hans Verkuil [this message]
2019-06-18 3:28 ` [PATCH v2 0/4] vicodec: a couple fixes towards spec compliancy Ezequiel Garcia
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=879d93cc-3777-bd61-5c14-34108fc8501a@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=ezequiel@collabora.com \
--cc=hans.verkuil@cisco.com \
--cc=kernel@collabora.com \
--cc=linux-media@vger.kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=tfiga@chromium.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).