From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexandre Courbot <acourbot@google.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org,
"Albert Esteve" <aesteve@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Andrew Gazizov" <andrew.gazizov@opensynergy.com>,
"Andrii Cherniavskyi" <andrii.cherniavskyi@opensynergy.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Enric Balletbo i Serra" <eballetb@redhat.com>,
"Enrico Granata" <egranata@google.com>,
"Gustavo Padovan" <gustavo.padovan@collabora.com>,
"Keiichi Watanabe" <keiichiw@chromium.org>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Alexander Gordeev" <alexander.gordeev@opensynergy.com>,
"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
"Peter Griffin" <peter.griffin@linaro.org>,
"Tomasz Figa" <tfiga@chromium.org>,
"Matti Möll" <Matti.Moell@opensynergy.com>
Subject: [virtio-comment] Re: virtio-v4l2 specification draft
Date: Wed, 31 May 2023 02:07:54 -0400 [thread overview]
Message-ID: <20230531020611-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAPBb6MXBaKKFGg8Yt2Me8kjUwCm4utWcsVOiCS1Qunjhza4Ycg@mail.gmail.com>
On Wed, May 31, 2023 at 03:02:04PM +0900, Alexandre Courbot wrote:
> Hello everyone,
>
> With the virtio-video call taking place soon, I thought it would help
> everyone understand both proposals if I sent a more formal
> specification of what virtio-v4l2 looks like. Please find it attached
> to this email.
>
> I apologize for not finishing and sending this earlier, but hopefully
> at 7 and a half pages it should be rather quick to skim through. :)
>
> Despite its short size, this spec is capable of supporting camera and
> image processor devices (on top of decoder/encoders), and also allows
> for another kind of memory backing for buffers (host-managed) that is
> not supported by virtio-video.
>
> For convenience I have made use of clickable links to the relevant
> parts of the V4L2 documentation, since it is supposed to be used
> alongside this spec.
>
> Looking forward to a fruitful discussion tomorrow!
>
> Cheers,
> Alex.
Can you please post patch with tex source inline as opposed as
pdf as an attachment? Thanks!
--
MST
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexandre Courbot <acourbot@google.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org,
"Albert Esteve" <aesteve@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Andrew Gazizov" <andrew.gazizov@opensynergy.com>,
"Andrii Cherniavskyi" <andrii.cherniavskyi@opensynergy.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Enric Balletbo i Serra" <eballetb@redhat.com>,
"Enrico Granata" <egranata@google.com>,
"Gustavo Padovan" <gustavo.padovan@collabora.com>,
"Keiichi Watanabe" <keiichiw@chromium.org>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Alexander Gordeev" <alexander.gordeev@opensynergy.com>,
"Kieran Bingham" <kieran.bingham@ideasonboard.com>,
"Peter Griffin" <peter.griffin@linaro.org>,
"Tomasz Figa" <tfiga@chromium.org>,
"Matti Möll" <Matti.Moell@opensynergy.com>
Subject: [virtio-dev] Re: virtio-v4l2 specification draft
Date: Wed, 31 May 2023 02:07:54 -0400 [thread overview]
Message-ID: <20230531020611-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAPBb6MXBaKKFGg8Yt2Me8kjUwCm4utWcsVOiCS1Qunjhza4Ycg@mail.gmail.com>
On Wed, May 31, 2023 at 03:02:04PM +0900, Alexandre Courbot wrote:
> Hello everyone,
>
> With the virtio-video call taking place soon, I thought it would help
> everyone understand both proposals if I sent a more formal
> specification of what virtio-v4l2 looks like. Please find it attached
> to this email.
>
> I apologize for not finishing and sending this earlier, but hopefully
> at 7 and a half pages it should be rather quick to skim through. :)
>
> Despite its short size, this spec is capable of supporting camera and
> image processor devices (on top of decoder/encoders), and also allows
> for another kind of memory backing for buffers (host-managed) that is
> not supported by virtio-video.
>
> For convenience I have made use of clickable links to the relevant
> parts of the V4L2 documentation, since it is supposed to be used
> alongside this spec.
>
> Looking forward to a fruitful discussion tomorrow!
>
> Cheers,
> Alex.
Can you please post patch with tex source inline as opposed as
pdf as an attachment? Thanks!
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next parent reply other threads:[~2023-05-31 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPBb6MXBaKKFGg8Yt2Me8kjUwCm4utWcsVOiCS1Qunjhza4Ycg@mail.gmail.com>
2023-05-31 6:07 ` Michael S. Tsirkin [this message]
2023-05-31 6:07 ` [virtio-dev] Re: virtio-v4l2 specification draft Michael S. Tsirkin
2023-07-06 8:27 ` Albert Esteve
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=20230531020611-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Matti.Moell@opensynergy.com \
--cc=acourbot@google.com \
--cc=aesteve@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alexander.gordeev@opensynergy.com \
--cc=andrew.gazizov@opensynergy.com \
--cc=andrii.cherniavskyi@opensynergy.com \
--cc=cohuck@redhat.com \
--cc=daniel.almeida@collabora.com \
--cc=eballetb@redhat.com \
--cc=egranata@google.com \
--cc=gustavo.padovan@collabora.com \
--cc=keiichiw@chromium.org \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=peter.griffin@linaro.org \
--cc=tfiga@chromium.org \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.