From: Ezequiel Garcia <ezequiel@collabora.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, 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: Tue, 18 Jun 2019 00:28:38 -0300 [thread overview]
Message-ID: <06161391ed2bbb0a2fc9085792b8db7c049d67db.camel@collabora.com> (raw)
In-Reply-To: <879d93cc-3777-bd61-5c14-34108fc8501a@xs4all.nl>
On Mon, 2019-06-17 at 14:43 +0200, Hans Verkuil wrote:
> 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.
>
Sure.
> > 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.
>
Sure, let me re-test it.
Thanks,
prev parent reply other threads:[~2019-06-18 3:28 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 ` [PATCH v2 0/4] vicodec: a couple fixes towards spec compliancy Hans Verkuil
2019-06-18 3:28 ` Ezequiel Garcia [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=06161391ed2bbb0a2fc9085792b8db7c049d67db.camel@collabora.com \
--to=ezequiel@collabora.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--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