From: Albert Esteve <aesteve@redhat.com>
To: virtio-dev@lists.linux.dev, virtio-dev@lists.oasis-open.org
Cc: Matti.Moell@opensynergy.com, cohuck@redhat.com, mst@redhat.com,
acourbot@chromium.org, daniel.almeida@collabora.com,
Alexander.Gordeev@opensynergy.com, changyeon@google.com,
alex.bennee@linaro.org, gurchetansingh@google.com,
ribalda@google.com, nicolas.dufresne@collabora.com,
eballetb@redhat.com, linux-media@vger.kernel.org,
virtio-comment@lists.oasis-open.org,
Albert Esteve <aesteve@redhat.com>
Subject: [PATCH v2 0/1] virtio-media: Add device specification
Date: Fri, 7 Jun 2024 10:00:44 +0200 [thread overview]
Message-ID: <20240607080045.1337046-1-aesteve@redhat.com> (raw)
Hi,
This a formal attempt of including virtio-media
device specification.
Virtio-media came from a discussion on virtio-dev
mailing list, which lead to presenting virtio-v4l2[1]
specification as an alternative to virtio-video.
Later, virtio-v4l2 was renamed to virtio-media[2]
and published through:
https://github.com/chromeos/virtio-media
The repository above includes a virtio-media driver able
to pass v4l2-compliance when proxying the vivid/vicodec
virtual devices or an actual UVC camera using the
V4L2 vhost device (available in the repository).
Steps to reproduce are also detailed[3].
There is some overlap with virtio-video in regards
to which devices it can handle. However,
as virtio-media will likely be the virtualization
solution for ChromeOS (already landed into the chromeos
organization) and possibly other Google projects for
media devices, it would be desirable to include the
specification in the next virtio release despite
the aforementioned overlap.
The device ID in this document differs from
the ID in the virtio-media project repository.
And it will probably need some discussion on which
would be the correct definitive ID.
Full PDF: https://drive.google.com/file/d/1pNCFP06VoV8Zuyx0aDVQ7HAT4xp-pZ0a/view?usp=sharing
PDF with the media section only: https://drive.google.com/file/d/1sn3NUUeCm46zVyJKHkpytTIgGw1fUt5T/view?usp=sharing
[1] https://mail.google.com/mail/u/0?ui=2&ik=73ebd65ebd&attid=0.1&permmsgid=msg-f:1767388565327924962&th=1887068940754ee2&view=att&disp=inline&realattid=f_libalimc0
[2] https://www.mail-archive.com/virtio-dev@lists.oasis-open.org/msg12665.html
[3] https://github.com/chromeos/virtio-media/blob/main/TRY_IT_OUT.md
Albert Esteve (1):
virtio-media: Add virtio media device specification
conformance.tex | 13 +-
content.tex | 1 +
device-types/media/description.tex | 578 ++++++++++++++++++++++
device-types/media/device-conformance.tex | 11 +
device-types/media/driver-conformance.tex | 9 +
5 files changed, 608 insertions(+), 4 deletions(-)
create mode 100644 device-types/media/description.tex
create mode 100644 device-types/media/device-conformance.tex
create mode 100644 device-types/media/driver-conformance.tex
--
2.44.0
next reply other threads:[~2024-06-07 8:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 8:00 Albert Esteve [this message]
2024-06-07 8:00 ` [PATCH v2 1/1] virtio-media: Add virtio media device specification Albert Esteve
2024-06-07 8:21 ` [PATCH v2 0/1] virtio-media: Add " Albert Esteve
2024-06-07 9:41 ` Michael S. Tsirkin
2024-06-07 9:48 ` Albert Esteve
2024-06-07 10:22 ` Michael S. Tsirkin
2024-06-07 10:54 ` Albert Esteve
2024-06-07 13:28 ` Alexander Gordeev
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=20240607080045.1337046-1-aesteve@redhat.com \
--to=aesteve@redhat.com \
--cc=Alexander.Gordeev@opensynergy.com \
--cc=Matti.Moell@opensynergy.com \
--cc=acourbot@chromium.org \
--cc=alex.bennee@linaro.org \
--cc=changyeon@google.com \
--cc=cohuck@redhat.com \
--cc=daniel.almeida@collabora.com \
--cc=eballetb@redhat.com \
--cc=gurchetansingh@google.com \
--cc=linux-media@vger.kernel.org \
--cc=mst@redhat.com \
--cc=nicolas.dufresne@collabora.com \
--cc=ribalda@google.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox