From: Dmitry Sepp <dmitry.sepp@opensynergy.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Samiullah Khawaja <samiullah.khawaja@opensynergy.com>,
Saket Sinha <saket.sinha89@gmail.com>,
Alex Lau <alexlau@chromium.org>,
Kiran Pawar <Kiran.Pawar@opensynergy.com>,
Alexandre Courbot <acourbot@chromium.org>,
virtio-dev@lists.oasis-open.org,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Keiichi Watanabe <keiichiw@chromium.org>,
libcamera-devel@lists.libcamera.org,
Gerd Hoffmann <kraxel@redhat.com>,
Pawel Osciak <posciak@chromium.org>,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [libcamera-devel] [virtio-dev] Re: Fwd: Qemu Support for Virtio Video V4L2 driver
Date: Tue, 12 May 2020 14:10:20 +0200 [thread overview]
Message-ID: <64045565.OWohDWQxgf@os-lin-dmo> (raw)
In-Reply-To: <20200511143136.GC5830@pendragon.ideasonboard.com>
Hi Laurent,
On Montag, 11. Mai 2020 16:31:36 CEST Laurent Pinchart wrote:
>
> I don't think this would be the right level of abstraction. The V4L2 API
> is way too low-level when it comes to camera paravirtualization (and may
> not be the only API we'll have in the future). I thus recommend
> virtualizing cameras with a higher-level API, more or less on top of
> libcamera or the Android camera HAL (they both sit at the same level in
> the camera stack). Anything lower than that won't be practical.
>
I think the the main thing to do first would be to define the logic of such
virtio-camera device and the set of mandatory features. Host-side API is a bit
of a side topic. But libcamera fits the best though.
Best regards,
Dmitry.
next prev parent reply other threads:[~2020-05-12 12:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 23:09 Qemu Support for Virtio Video V4L2 driver Saket Sinha
2020-05-09 14:09 ` Saket Sinha
2020-05-09 14:11 ` Fwd: " Saket Sinha
2020-05-11 9:40 ` Dmitry Sepp
2020-05-11 10:20 ` [virtio-dev] " Keiichi Watanabe
2020-05-11 11:05 ` Saket Sinha
2020-05-11 11:25 ` Dmitry Sepp
2020-05-11 11:32 ` Michael S. Tsirkin
2020-05-11 11:34 ` Michael S. Tsirkin
2020-05-11 11:49 ` Keiichi Watanabe
2020-05-11 12:32 ` Saket Sinha
2020-05-11 14:06 ` Keiichi Watanabe
2020-05-11 14:31 ` [libcamera-devel] " Laurent Pinchart
2020-05-12 12:10 ` Dmitry Sepp [this message]
2020-05-14 23:38 ` Nicolas Dufresne
2020-05-19 8:37 ` Keiichi Watanabe
2020-05-19 17:29 ` Nicolas Dufresne
2020-05-20 3:19 ` Alexandre Courbot
2020-05-20 16:21 ` Nicolas Dufresne
2020-05-20 16:27 ` Michael S. Tsirkin
2020-05-20 16:56 ` Nicolas Dufresne
2020-05-21 7:08 ` Alexandre Courbot
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=64045565.OWohDWQxgf@os-lin-dmo \
--to=dmitry.sepp@opensynergy.com \
--cc=Kiran.Pawar@opensynergy.com \
--cc=acourbot@chromium.org \
--cc=alexlau@chromium.org \
--cc=keiichiw@chromium.org \
--cc=kraxel@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=libcamera-devel@lists.libcamera.org \
--cc=linux-media@vger.kernel.org \
--cc=mst@redhat.com \
--cc=posciak@chromium.org \
--cc=qemu-devel@nongnu.org \
--cc=saket.sinha89@gmail.com \
--cc=samiullah.khawaja@opensynergy.com \
--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;
as well as URLs for NNTP newsgroup(s).