From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Thayer <michael.thayer@oracle.com>
Cc: daniel.vetter@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm: remove immutable flag from suggested X/Y connector properties
Date: Tue, 03 Jan 2017 11:40:50 +0100 [thread overview]
Message-ID: <1483440050.24493.23.camel@redhat.com> (raw)
In-Reply-To: <c71925d5-3baa-ca3f-26c7-b33a5373f1c1@oracle.com>
Hi,
> > Makes sense I think, but for merging we need:
> > - some driver to implement
>
> This is where it starts getting tricky. vboxvideo is out of tree. In
> theory I could look at getting it merged, but that needs time I am
> rather short of (I am the only person maintaining that driver and it is
> just one of my responsibilities; and there are some bits there that are
> probably too ugly to merge as is). I don't think I am really the person
> to be doing this for qxl/virtio-gpu as that required adding the support
> to qemu too.
Not only kernel driver and qemu. Right now neither qxl nor virtio-gpu
can communicate the actual layout back to the host. So this also
requires changes to the guest/host protocol (i.e. the virtual hardware).
> > - some userspace to take advantage of it
>
> As I wrote, mutter would be the first candidate.
Do you have any feedback from mutter developers on the two approaches
(touchscreen-style autoconfig or x+y offsets)?
cheers,
Gerd
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-03 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 10:38 [PATCH] drm: remove immutable flag from suggested X/Y connector properties Michael Thayer
2016-12-21 9:05 ` Daniel Vetter
2016-12-21 14:30 ` Michael Thayer
2016-12-22 7:07 ` Daniel Vetter
2016-12-22 7:46 ` Michael Thayer
2017-01-03 10:40 ` Gerd Hoffmann [this message]
2017-01-04 17:49 ` 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=1483440050.24493.23.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=daniel.vetter@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox