From: "Alexandre Courbot" <gnurou@gmail.com>
To: "Albert Esteve" <aesteve@redhat.com>, <virtio-comment@lists.linux.dev>
Cc: <nicolas.dufresne@collabora.com>, <cohuck@redhat.com>,
<adelva@google.com>, <mvaralar@redhat.com>, <hverkuil@xs4all.nl>,
<mst@redhat.com>, <dverkamp@chromium.org>,
<gurchetansingh@google.com>, <alex.bennee@linaro.org>,
<changyeon@google.com>, <daniel.almeida@collabora.com>,
<agordeev@qti.qualcomm.com>, <eballetb@redhat.com>,
<ribalda@google.com>
Subject: Re: [PATCH v8 1/1] virtio-media: Add virtio media device specification
Date: Fri, 14 Mar 2025 22:25:54 +0900 [thread overview]
Message-ID: <D8G0UC5KFCYY.32BN79B9WOK33@gmail.com> (raw)
In-Reply-To: <20250304130134.1856056-2-aesteve@redhat.com>
Hello Albert,
On Tue Mar 4, 2025 at 10:01 PM JST, Albert Esteve wrote:
> Virtio-media is an encapsulation of the V4L2 UAPI into
> virtio, able to virtualize any video device supported
> by V4L2.
>
> Note that virtio-media does not require the use of a
> V4L2 device driver on the host or guest side -
> V4L2 is only used as a host-guest protocol,
> and both sides are free to convert it from/to any
> model that they wish to use.
Thank you for your patience with this. I have done a final pass on this
version and it looks great to me!
Reviewed-by: Alexandre Courbot <gnurou@gmail.com>
next prev parent reply other threads:[~2025-03-14 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 13:01 [PATCH v8 0/1] virtio-media: Add device specification Albert Esteve
2025-03-04 13:01 ` [PATCH v8 1/1] virtio-media: Add virtio media " Albert Esteve
2025-03-14 13:25 ` Alexandre Courbot [this message]
2025-03-18 9:02 ` Albert Esteve
2025-07-09 9:31 ` Alex Bennée
2025-07-09 9:38 ` Albert Esteve
2025-07-09 12:09 ` Albert Esteve
2025-07-09 12:18 ` Albert Esteve
2025-07-09 13:29 ` Parav Pandit
2025-07-09 13:43 ` 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=D8G0UC5KFCYY.32BN79B9WOK33@gmail.com \
--to=gnurou@gmail.com \
--cc=adelva@google.com \
--cc=aesteve@redhat.com \
--cc=agordeev@qti.qualcomm.com \
--cc=alex.bennee@linaro.org \
--cc=changyeon@google.com \
--cc=cohuck@redhat.com \
--cc=daniel.almeida@collabora.com \
--cc=dverkamp@chromium.org \
--cc=eballetb@redhat.com \
--cc=gurchetansingh@google.com \
--cc=hverkuil@xs4all.nl \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=nicolas.dufresne@collabora.com \
--cc=ribalda@google.com \
--cc=virtio-comment@lists.linux.dev \
/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.