public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: Albert Esteve <aesteve@redhat.com>
To: virtio-comment@lists.linux.dev
Cc: changyeon@google.com, daniel.almeida@collabora.com,
	ribalda@google.com, nicolas.dufresne@collabora.com,
	alex.bennee@linaro.org, eballetb@redhat.com,
	acourbot@chromium.org, gurchetansingh@google.com,
	hverkuil@xs4all.nl, cohuck@redhat.com, mst@redhat.com,
	agordeev@qti.qualcomm.com, Albert Esteve <aesteve@redhat.com>
Subject: [PATCH v3 0/1] virtio-media: Add device specification
Date: Thu, 17 Oct 2024 09:04:22 +0200	[thread overview]
Message-ID: <20241017070423.86706-1-aesteve@redhat.com> (raw)

New attempt of including virtio-media
device specification.

v2->v3:
- Updated device ID to 49
- Renamed virtio memory types so that
  they are differentiated from V4L2
  memory types
- Memory types description slightly
  rewritten, explicitely excluding
  USERPTR support for guest userspace

v1->v2:
- Remove naming host/guest in the text
- Explicitly specify endian-ness of the device
- Change address by offset in the MMAP operation
- Specify SHM region for MMAP operation

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 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 got a proposal to reserve
device ID 49, 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, making them
the preferable choice for different scenarios.
Moreover, 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 is justified the desire to include
the specification in the next release despite
the aforementioned overlap.

Full PDF: https://drive.google.com/file/d/1zhmteCqkZsn-oQz5Gle2uG8HvDy1vGSw/view?usp=sharing
PDF with the media section only: https://drive.google.com/file/d/19A8RH-3kiOkod0xkHkuxCtoq0-PtuaQ4/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        | 583 ++++++++++++++++++++++
 device-types/media/device-conformance.tex |  11 +
 device-types/media/driver-conformance.tex |   9 +
 5 files changed, 613 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.47.0


             reply	other threads:[~2024-10-17  7:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17  7:04 Albert Esteve [this message]
2024-10-17  7:04 ` [PATCH v3 1/1] virtio-media: Add virtio media device specification Albert Esteve
2024-10-17 20:02   ` Daniel Verkamp
2024-10-21  8:03     ` Albert Esteve
2024-10-18  8:52   ` Matias Ezequiel Vara Larsen
2024-10-21 13:21     ` Albert Esteve
2024-10-18 10:12   ` Parav Pandit
2024-10-21  7:49     ` Albert Esteve
     [not found]   ` <CAPBb6MXZ0mtniEDiBnbYE1zDgTAYCvQ2-g-9TxaD3t3AzwZiOQ@mail.gmail.com>
2024-10-21 13:42     ` Albert Esteve
     [not found]       ` <CAPBb6MV9WT=tF0rk0dX_hr3SaHFqxzNf=MZDDRPauvpkYqRrZg@mail.gmail.com>
2024-10-23  6:39         ` 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=20241017070423.86706-1-aesteve@redhat.com \
    --to=aesteve@redhat.com \
    --cc=acourbot@chromium.org \
    --cc=agordeev@qti.qualcomm.com \
    --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=hverkuil@xs4all.nl \
    --cc=mst@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