Re: [virtio-dev] Re: [RFC PATCH v6] virtio-video: Add virtio video device specification

[Cornelia Huck <cohuck@redhat.com>]

On Mon, Apr 17 2023, Alexander Gordeev <alexander.gordeev@opensynergy.com> wrote:

> Hello Cornelia,
>
> On 17.04.23 14:56, Cornelia Huck wrote:
>> On Sat, Apr 15 2023, Alexandre Courbot <acourbot@chromium.org> wrote:
>>
>>> If nobody strongly objects, I think this can be pushed a bit more
>>> officially. Cornelia, would you consider it for inclusion if I
>>> switched the next version of the specification to use V4L2 as the
>>> host/guest protocol? This may take some more time as I want to confirm
>>> the last details with code, but it should definitely be faster to
>>> merge and to test with a real implementation than our previous
>>> virtio-video attempts.
>> Yes, please do post a new version of this spec; I agree that an existing
>> implementation is really helpful here.
>>
>> [I have proposed July 1st as a "freeze" date for new features for 1.3,
>> with August 1st as an "everything must be in" date; I'd really like
>> virtio-video to be a part of 1.3, if possible :)]
>
> I sent an email minutes ago with an alternative plan. I'd like to
> volunteer to continue the evolutionary changes to virtio-video. I'm
> already working on the v7 draft. I think it will be available next week.
> Then I'll focus on making the driver V4L2 compliant. I think all of this
> is achievable by July 1st. At least the spec part. I think the
> revolutionary changes should be in a separate namespace. The rationale
> is in the longer email. WDYT?

Seems our mails crossed mid-air... I'll go ahead and read your mail (and
probably answer there.) My ultimate goal is to have a spec everyone is
happy with, regardless on how we arrive there.