From: Albert Esteve <aesteve@redhat.com>
To: virtio-comment@lists.linux.dev
Cc: ribalda@google.com, alex.bennee@linaro.org, adelva@google.com,
cohuck@redhat.com, mvaralar@redhat.com, hverkuil@xs4all.nl,
gurchetansingh@google.com, daniel.almeida@collabora.com,
changyeon@google.com, acourbot@google.com, mst@redhat.com,
eballetb@redhat.com, agordeev@qti.qualcomm.com, gnurou@gmail.com,
dverkamp@chromium.org, nicolas.dufresne@collabora.com,
Albert Esteve <aesteve@redhat.com>
Subject: [PATCH v9 0/1] virtio-media: Add device specification
Date: Wed, 9 Jul 2025 11:34:55 +0200 [thread overview]
Message-ID: <20250709093456.350242-1-aesteve@redhat.com> (raw)
New attempt of including virtio-media
device specification.
v8->v9:
- Rebased to virtio-1.4
v7->v8:
- Merged DQBUF and DQEVENT into the same
item for unsupported ioctls
- Rewrote/clarified a couple paragraphs
based on previous version reviews.
Virtio-media came from a discussion on virtio-dev
mailing list, which lead to Alex Courbot presenting
virtio-v4l2[1] specification as an alternative to
virtio-video.
Later, virtio-v4l2 was renamed to virtio-media[2]
and published at:
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).
It also includes a FFmpeg-based video encoder
device. Steps to reproduce are also detailed[3].
Recently, virtio-media has landed in AOSP[4].
Also the driver patch has been sent to the
kernel, currently in its v2 [5].
Furthermore, virtio-media got a proposal to reserve
device ID 48, which was finally approved for
inclusion in v1.4.
There is some overlap with virtio-video in regards
to which devices it can handle. However, they take
different approaches, potentially making them
the preferable choice for different scenarios.
Furthermore, virtio-media has matured since it
was first presented, and there are public efforts
to have upstream driver and devices.
But mainly, given that virtio-media will be the virtualization
solution for media devices for ChromeOS, Android, and
possibly others, I think is important that it gets
standardized and included in the specification,
despite the aforementioned overlap.
Full PDF: https://drive.google.com/file/d/1sDZXWVlvPbHKKguhekCXMzkpNZZ0g3hV/view?usp=sharing
PDF with the media section only: https://drive.google.com/file/d/1JjOIzecnkFFlpFBRjPQEUyAOD3BDHAdw/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
[4] https://cs.android.com/android/platform/superproject/main/+/main:external/virtio-media/
[5] https://lore.kernel.org/lkml/20250201-virtio-media-v2-1-ac840681452d@gmail.com/T/
Albert Esteve (1):
virtio-media: Add virtio media device specification
conformance.tex | 6 +
content.tex | 1 +
device-types/media/description.tex | 639 ++++++++++++++++++++++
device-types/media/device-conformance.tex | 15 +
device-types/media/driver-conformance.tex | 11 +
5 files changed, 672 insertions(+)
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.49.0
next reply other threads:[~2025-07-09 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 9:34 Albert Esteve [this message]
2025-07-09 9:34 ` [PATCH v9 1/1] virtio-media: Add virtio media device specification Albert Esteve
2025-07-09 9:44 ` [PATCH v9 0/1] virtio-media: Add " Matias Ezequiel Vara Larsen
2025-07-09 9:49 ` Parav Pandit
2025-07-09 10:01 ` Albert Esteve
2025-07-09 10:05 ` Parav Pandit
2025-07-09 17:26 ` Demi Marie Obenour
[not found] ` <acc37ff248e70493a8068d8fc8c810effdc44093.camel@collabora.com>
2025-07-09 19:48 ` Demi Marie Obenour
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=20250709093456.350242-1-aesteve@redhat.com \
--to=aesteve@redhat.com \
--cc=acourbot@google.com \
--cc=adelva@google.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=gnurou@gmail.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).