Re: [PATCH 0/2] vhost-user-gpu get_edid feature

On 24/05/2023 13:23, Marc-André Lureau wrote: > Hi Erico > > On Wed, May 17, 2023 at 8:09 PM Erico Nunes > wrote: > > On 15/05/2023 13:38, Marc-André Lureau wrote: > > However, I worry about using the new backend (calling GET_EDID) > with an > > older f

Re: [PATCH 0/2] vhost-user-gpu get_edid feature

Hi Erico On Wed, May 17, 2023 at 8:09 PM Erico Nunes wrote: > On 15/05/2023 13:38, Marc-André Lureau wrote: > > However, I worry about using the new backend (calling GET_EDID) with an > > older front-end/QEMU. It may just hang, since > > vhost_user_gpu_handle_display() won't reply to unknown mes

Re: [PATCH 0/2] vhost-user-gpu get_edid feature

On 15/05/2023 13:38, Marc-André Lureau wrote: > However, I worry about using the new backend (calling GET_EDID) with an > older front-end/QEMU. It may just hang, since > vhost_user_gpu_handle_display() won't reply to unknown messages. That's > what PROTOCOL_FEATURES were meant for, iirc. Can you ch

Re: [PATCH 0/2] vhost-user-gpu get_edid feature

Hi On Thu, May 11, 2023 at 5:02 PM Erico Nunes wrote: > This adds support to the virtio-gpu get_edid command when using the > vhost-user-gpu implementation in contrib/. > So far, qemu has been outputting the following message: > EDID requested but the backend doesn't support it. > when using t

[PATCH 0/2] vhost-user-gpu get_edid feature

This adds support to the virtio-gpu get_edid command when using the vhost-user-gpu implementation in contrib/. So far, qemu has been outputting the following message: EDID requested but the backend doesn't support it. when using that implementation. This is tested with vhost-user-gpu, the dbus u