Dmitry Osipenko writes:
> On 2/17/25 18:22, Alex Bennée wrote:
> ...
>>> This VK_KHR_display problem is only reproducible with your rootfs that
>>> you shared with me. It could be a trouble with your build configs or a
>>> buggy package version used by your rootfs build, more likely the
>>> forme
On 2/17/25 18:22, Alex Bennée wrote:
...
>> This VK_KHR_display problem is only reproducible with your rootfs that
>> you shared with me. It could be a trouble with your build configs or a
>> buggy package version used by your rootfs build, more likely the
>> former.
> So you have built that latest
Dmitry Osipenko writes:
> On 2/14/25 17:33, Alex Bennée wrote:
>> Dmitry Osipenko writes:
>>
>>> This patchset adds DRM native context support to VirtIO-GPU on Qemu.
>>>
>>> Contarary to Virgl and Venus contexts that mediates high level GFX APIs,
>>> DRM native context [1] mediates lower level
Dmitry Osipenko writes:
> On 1/27/25 19:17, Alex Bennée wrote:
>> Dmitry Osipenko writes:
>>
>>> This patchset adds DRM native context support to VirtIO-GPU on Qemu.
>>>
>>> Contarary to Virgl and Venus contexts that mediates high level GFX APIs,
>>> DRM native context [1] mediates lower level
On 2/14/25 17:33, Alex Bennée wrote:
> Dmitry Osipenko writes:
>
>> This patchset adds DRM native context support to VirtIO-GPU on Qemu.
>>
>> Contarary to Virgl and Venus contexts that mediates high level GFX APIs,
>> DRM native context [1] mediates lower level kernel driver UAPI, which
>> refle
Dmitry Osipenko writes:
> This patchset adds DRM native context support to VirtIO-GPU on Qemu.
>
> Contarary to Virgl and Venus contexts that mediates high level GFX APIs,
> DRM native context [1] mediates lower level kernel driver UAPI, which
> reflects in a less CPU overhead and less/simpler co
Hi Dmitry,
> Subject: Re: [PATCH v6 00/10] Support virtio-gpu DRM native context
>
> On 2/6/25 01:13, Dmitry Osipenko wrote:
> > On 2/5/25 23:08, Dmitry Osipenko wrote:
> >>> Thanks for showing me the video. I will take a look and check what would
> go wrong here.
On 2/6/25 01:13, Dmitry Osipenko wrote:
> On 2/5/25 23:08, Dmitry Osipenko wrote:
>>> Thanks for showing me the video. I will take a look and check what would go
>>> wrong here. I kinda understand corruption may happen
>>> in some scenario but I don't know what could cause the upside down image.
On 2/5/25 23:08, Dmitry Osipenko wrote:
>> Thanks for showing me the video. I will take a look and check what would go
>> wrong here. I kinda understand corruption may happen
>> in some scenario but I don't know what could cause the upside down image. Do
>> you have any idea?? Maybe the frame was
On 2/5/25 21:53, Kim, Dongwon wrote:
> Thanks for showing me the video. I will take a look and check what would go
> wrong here. I kinda understand corruption may happen
> in some scenario but I don't know what could cause the upside down image. Do
> you have any idea?? Maybe the frame was tempor
(like minimization).
> Subject: Re: [PATCH v6 00/10] Support virtio-gpu DRM native context
>
> On 2/4/25 04:51, Kim, Dongwon wrote:
> >> Subject: Re: [PATCH v6 00/10] Support virtio-gpu DRM native context
> >>
> >> "Kim, Dongwon" writes:
> >>
>
On 2/4/25 04:51, Kim, Dongwon wrote:
>> Subject: Re: [PATCH v6 00/10] Support virtio-gpu DRM native context
>>
>> "Kim, Dongwon" writes:
>>
>>> Hi,
>>>
>>> The commit below could change the timing of drawing by making the
>>
> Subject: Re: [PATCH v6 00/10] Support virtio-gpu DRM native context
>
> "Kim, Dongwon" writes:
>
> > Hi,
> >
> > The commit below could change the timing of drawing by making the
> > drawing done at refresh cycle instead of via drawing event.
e. Hey, can
> you
> describe how the corruption looks like? Is it just garbage image with random
> noise
> or the actual frame with some defects like tearing...?
The terminal gets mirrored upside down and the mouse creates damage as
it moves about.
>
>> Subject: Re:
just garbage image with random
noise
or the actual frame with some defects like tearing...?
> Subject: Re: [PATCH v6 00/10] Support virtio-gpu DRM native context
>
> Dmitry Osipenko writes:
>
> > On 1/27/25 19:17, Alex Bennée wrote:
> > ...
> >> I'm still s
Dmitry Osipenko writes:
> On 1/27/25 19:17, Alex Bennée wrote:
> ...
>> I'm still seeing corruption with -display gtk,gl=on on my x86 system
>> BTW. I would like to understand if that is a problem with QEMU, GTK or
>> something else in the stack before we merge.
>
> I reproduced the display mirro
On 1/27/25 19:17, Alex Bennée wrote:
...
> I'm still seeing corruption with -display gtk,gl=on on my x86 system
> BTW. I would like to understand if that is a problem with QEMU, GTK or
> something else in the stack before we merge.
I reproduced the display mirroring/corruption issue and bisected i
On 1/27/25 19:17, Alex Bennée wrote:
> Dmitry Osipenko writes:
>
>> This patchset adds DRM native context support to VirtIO-GPU on Qemu.
>>
>> Contarary to Virgl and Venus contexts that mediates high level GFX APIs,
>> DRM native context [1] mediates lower level kernel driver UAPI, which
>> refle
Dmitry Osipenko writes:
> This patchset adds DRM native context support to VirtIO-GPU on Qemu.
>
> Contarary to Virgl and Venus contexts that mediates high level GFX APIs,
> DRM native context [1] mediates lower level kernel driver UAPI, which
> reflects in a less CPU overhead and less/simpler co
This patchset adds DRM native context support to VirtIO-GPU on Qemu.
Contarary to Virgl and Venus contexts that mediates high level GFX APIs,
DRM native context [1] mediates lower level kernel driver UAPI, which
reflects in a less CPU overhead and less/simpler code needed to support it.
DRM contex
20 matches
Mail list logo
