[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 14/27] ui: add a D-Bus display backend
|
From: |
Gerd Hoffmann |
|
Subject: |
Re: [PATCH 14/27] ui: add a D-Bus display backend |
|
Date: |
Fri, 12 Mar 2021 16:16:02 +0100 |
> On Fri, Mar 12, 2021 at 3:03 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> > Hi,
> >
> > > The "dbus" ui/display backend exports the QEMU consoles over a currently
> > > unstable D-Bus protocol defined in ui/dbus-display1.xml (it is subject
> > > to changes at each releases, so only client shipped with the same QEMU
> > > release will be fully compatible).
> >
> > Hmm, so we get a new protocol here.
> >
> > A different idea which crossed my mind after reading the pipewire
> > article of last weeks lwn.net edition: pipewire has video support.
> > It also has audio support. gnome uses it for remote desktop support,
> > so support for cursors and mouse/keyboard backchannel should be there
> > too.
> >
> > In other words: pipewire should have all the pieces needed to build a
> > qemu UI with it.
> >
> > I haven't found the time yet to investigate more, but integrating qemu
> > with pipewire looks much more attractive to me than inventing a new
> > protocol ...
> Perhaps that could work for audio & video (where is the protocol defined?).
Dunno. I'd go for the library though (simliar to pulseaudio, you'll go
use the libraries instead of talking to the pulse daemon directly).
Documentation starting point is https://pipewire.org/#documentation
> But what about the rest? input events, consoles, usb redirection, etc.
I expect input events are being there (how else should a remote desktop
work?), but didn't came that far yet in wading through the docs. Dunno
for console and usb redirection. Maybe it is possible to create custom
data channels.
> Remember the goal is to be able to implement any display backend in a
> standalone project.
Yes. With pipewire I hope to get nice integration with everything
speaking pipewire in addition to that. Like firefox being able to
use a virtual machine display for desktop sharing.
But maybe it works better in the end if a pipewire bridge is built as
standalone display backend based on this new dbus protocol.
take care,
Gerd
- Re: [PATCH 07/27] ui: make gl_block use a counter, (continued)
- [PATCH 08/27] ui: add a gl-unblock warning timer, marcandre . lureau, 2021/03/12
- [PATCH 09/27] ui: simplify gl unblock & flush, marcandre . lureau, 2021/03/12
- [PATCH 10/27] ui: dispatch GL events to all listeners, marcandre . lureau, 2021/03/12
- [PATCH 11/27] ui: split the GL context in a different object, marcandre . lureau, 2021/03/12
- [PATCH 12/27] ui: move qemu_spice_fill_device_address to ui/util.c, marcandre . lureau, 2021/03/12
- [PATCH 13/27] console: save current scanout details, marcandre . lureau, 2021/03/12
- [PATCH 14/27] ui: add a D-Bus display backend, marcandre . lureau, 2021/03/12
- [PATCH 15/27] audio: add dbusaudio backend, marcandre . lureau, 2021/03/12
- [PATCH 16/27] vhost-user-gpu: add vg_send_disable_scanout(), marcandre . lureau, 2021/03/12
- [PATCH 17/27] vhost-user-gpu: add vg_send_scanout_dmabuf(), marcandre . lureau, 2021/03/12
- [PATCH 18/27] vhost-user-gpu: add vg_send_dmabuf_update(), marcandre . lureau, 2021/03/12
- [PATCH 19/27] vhost-user-gpu: add vg_send_scanout(), marcandre . lureau, 2021/03/12
- [PATCH 20/27] vhost-user-gpu: add vg_send_cursor_update(), marcandre . lureau, 2021/03/12
- [PATCH 21/27] vhost-user-gpu: add vg_send_cursor_pos(), marcandre . lureau, 2021/03/12
- [PATCH 22/27] vhost-user-gpu: add vg_send_update(), marcandre . lureau, 2021/03/12
- [PATCH 23/27] vhost-user: add VHOST_USER_GPU_QEMU_DBUS_LISTENER, marcandre . lureau, 2021/03/12
- [PATCH 24/27] ui: add GraphicHwOps.register_dbus_listener(), marcandre . lureau, 2021/03/12