From: Dmitry Sepp <dmitry.sepp@opensynergy.com>
To: Kiran Pawar <Kiran.Pawar@opensynergy.com>,
Samiullah Khawaja <samiullah.khawaja@opensynergy.com>,
<qemu-devel@nongnu.org>, Saket Sinha <saket.sinha89@gmail.com>
Cc: virtio-dev@lists.oasis-open.org,
Gerd Hoffmann <kraxel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: Fwd: Qemu Support for Virtio Video V4L2 driver
Date: Mon, 11 May 2020 11:40:22 +0200 [thread overview]
Message-ID: <2405792.XL1faGB9W5@os-lin-dmo> (raw)
In-Reply-To: <CAK25hWOPS1wGORXgtv8hUNu9-mLO+5C_k3Cj=8pnoFWmjuhJdg@mail.gmail.com>
Hi Saket and all,
As we are working with automotive platforms, unfortunately we don't plan any
Qemu reference implementation so far.
Of course we are ready to support the community if any help is needed. Is
there interest in support for the FWHT format only for testing purpose or you
want a full-featured implementation on the QEMU side?
Please note that the spec is not finalized yet and a major update is now
discussed with upstream and the Chrome OS team, which is also interested and
deeply involved in the process. The update mostly implies some rewording and
reorganization of data structures, but for sure will require a driver rework.
Best regards,
Dmitry.
On Samstag, 9. Mai 2020 16:11:43 CEST Saket Sinha wrote:
> Hi,
>
> As suggested on #qemu-devel IRC channel, I am including virtio-dev, Gerd and
> Michael to point in the right direction how to move forward with Qemu
> support for Virtio Video V4L2 driver
> posted in [1].
>
> [1]: https://patchwork.linuxtv.org/patch/61717/
>
> Regards,
> Saket Sinha
>
> On Sat, May 9, 2020 at 1:09 AM Saket Sinha <saket.sinha89@gmail.com> wrote:
> > Hi ,
> >
> > This is to inquire about Qemu support for Virtio Video V4L2 driver
> > posted in [1].
> > I am currently not aware of any upstream effort for Qemu reference
> > implementation and would like to discuss how to proceed with the same.
> >
> > [1]: https://patchwork.linuxtv.org/patch/61717/
> >
> > Regards,
> > Saket Sinha
next prev parent reply other threads:[~2020-05-11 14:10 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 [this message]
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
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=2405792.XL1faGB9W5@os-lin-dmo \
--to=dmitry.sepp@opensynergy.com \
--cc=Kiran.Pawar@opensynergy.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--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).