All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Thayer <michael.thayer@oracle.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: Passing multi-screen layout to KMS driver
Date: Wed, 14 Dec 2016 11:11:26 +0100	[thread overview]
Message-ID: <1481710286.8440.42.camel@redhat.com> (raw)
In-Reply-To: <52299408-a71b-de15-ed2e-9e18617de408@oracle.com>

  Hi,

> So I would be interested to know whether anyone else has thought about 
> this problem, and possibly even about an interface to let the compositor 
> pass the information.  If not, would people be open to the idea?  I 
> would much rather have something generally agreed on than hack something up.

I think the best way to tackle this is to have multiple tablets, one per
display device (touchscreen-style setup).

qemu can do that, with input routing (must configure on the host which
display belongs to which tablet).  Here is some info on that:

http://git.qemu-project.org/?p=qemu.git;a=blob;f=docs/multiseat.txt;hb=HEAD

The setup on the guest side is completely manual.  You have to use
"xinput --map-to-output" to tell Xorg which tablet belongs to which
display.  Maybe it is also possible to stick that into xorg.conf.
Should be improved, and it surely makes sense that qemu and virtualbox
use the same approach here.

Not sure if and how this works automatically with physical touchscreens.
Any clues are welcome.

Another option is to use a guest agent, spice does that since years to
handle multihead.  The guest agent queries the display layout using
xrandr, gets x + y + displayid from the spice client and generates
pointer events from that.  But I expect that scheme breaks with wayland
because wayland is by design alot more restrictive, so spice-agent
probably isn't allowed to send pointer events.  So not really an option
these days ...

cheers,
  Gerd

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-12-14 10:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-13 19:59 Passing multi-screen layout to KMS driver Michael Thayer
2016-12-14 10:11 ` Gerd Hoffmann [this message]
2016-12-15 14:03   ` Michael Thayer
2016-12-16 11:33     ` Michael Thayer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1481710286.8440.42.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=michael.thayer@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.