On Wed, Jul 8, 2020 at 6:35 AM Alexandre Courbot wrote:
>
> On Fri, Jul 3, 2020 at 6:55 PM Tomasz Figa wrote:
> >
> > On Fri, Jul 3, 2020 at 11:27 AM Alexandre Courbot
> > wrote:
> > >
> > > On Fri, Jul 3, 2020 at 6:18 PM Michael S. Tsirkin wrote:
> > > >
> > > > On Fri, Jul 03, 2020 at 02:45:
On Fri, Jul 3, 2020 at 6:55 PM Tomasz Figa wrote:
>
> On Fri, Jul 3, 2020 at 11:27 AM Alexandre Courbot
> wrote:
> >
> > On Fri, Jul 3, 2020 at 6:18 PM Michael S. Tsirkin wrote:
> > >
> > > On Fri, Jul 03, 2020 at 02:45:15PM +0900, Alexandre Courbot wrote:
> > > > Hi Dmitry,
> > > >
> > > > On
Hi Alexandre, Tomasz,
Thank you very much for your feedback.
Yes, unfortunately we cannot disable dmabuf mode as it is currently mandatory
for Android.
AFAIU the work to have this ready in the main v4l2 spec requires time. But in
the virtio-video spec we indeed can mention something like that
On Fri, Jul 03, 2020 at 02:45:15PM +0900, Alexandre Courbot wrote:
> Hi Dmitry,
>
> On Thu, Jul 2, 2020 at 10:47 PM Dmitry Sepp
> wrote:
> >
> > Hi Keiichi,
> >
> > Thanks for the clarification. I believe we should explicitly describe this
> > in
> > the VIRTIO_VIDEO_CMD_RESOURCE_ATTACH section
On Fri, Jul 3, 2020 at 11:27 AM Alexandre Courbot wrote:
>
> On Fri, Jul 3, 2020 at 6:18 PM Michael S. Tsirkin wrote:
> >
> > On Fri, Jul 03, 2020 at 02:45:15PM +0900, Alexandre Courbot wrote:
> > > Hi Dmitry,
> > >
> > > On Thu, Jul 2, 2020 at 10:47 PM Dmitry Sepp
> > > wrote:
> > > >
> > > >
On Fri, Jul 3, 2020 at 6:18 PM Michael S. Tsirkin wrote:
>
> On Fri, Jul 03, 2020 at 02:45:15PM +0900, Alexandre Courbot wrote:
> > Hi Dmitry,
> >
> > On Thu, Jul 2, 2020 at 10:47 PM Dmitry Sepp
> > wrote:
> > >
> > > Hi Keiichi,
> > >
> > > Thanks for the clarification. I believe we should expl
Hi Dmitry,
On Thu, Jul 2, 2020 at 10:47 PM Dmitry Sepp wrote:
>
> Hi Keiichi,
>
> Thanks for the clarification. I believe we should explicitly describe this in
> the VIRTIO_VIDEO_CMD_RESOURCE_ATTACH section. And I also still see a problem
> there. If it is a guest allocated resource, we cannot co
Hi Dmitry,
On Thu, Jul 2, 2020 at 4:32 PM Dmitry Sepp wrote:
>
> Hi Keiichi,
>
> Thank you very much for the hard work to update the spec and to summarize all
> of the recent proposals!
>
> I want to again raise a topic that was discussed earlier and unfortunately the
> latest proposal cannot res
Hi Keiichi,
Thanks for the clarification. I believe we should explicitly describe this in
the VIRTIO_VIDEO_CMD_RESOURCE_ATTACH section. And I also still see a problem
there. If it is a guest allocated resource, we cannot consider it to be free
until the device really releases it. And it won't h
Hi Keiichi,
Thank you very much for the hard work to update the spec and to summarize all
of the recent proposals!
I want to again raise a topic that was discussed earlier and unfortunately the
latest proposal cannot resolve the problem. I hope together with upstream
people we'll be able to fi
This is the v4 RFC of virtio video device specification.
PDF versions are available at [1, 2].
Note that this patch depends on a recent patchset "Cross-device resource
sharing" [3].
Here is a list of major changes from v3:
* Redesingned struct definitions for each command and request based on
d
11 matches
Mail list logo
