Hi On Fri, Mar 12, 2021 at 3:03 PM Gerd Hoffmann <kra...@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?). But what about the rest? input events, consoles, usb redirection, etc. Remember the goal is to be able to implement any display backend in a standalone project. Eventually, the RegisterListener & Listener interface could become RegisterPipewireListener for example.
