From: Thomas Hellstrom <thomas@shipmail.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>,
linux-graphics-maintainer@vmware.com,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: Exposing monitor layout to desktop managers
Date: Thu, 11 Dec 2014 13:09:40 +0100 [thread overview]
Message-ID: <54898984.1090003@shipmail.org> (raw)
In-Reply-To: <CAPM=9tzJ8AGwVhq7ifpAJ1hW+PPbWMw3d2jAE-76vxtJzp_DCA@mail.gmail.com>
On 12/11/2014 12:57 PM, Dave Airlie wrote:
> On 11 December 2014 at 20:58, Thomas Hellstrom <thomas@shipmail.org> wrote:
>> Hi!
>>
>> I'd like to have a standard / generic way of exposing virtual monitor
>> layout to desktop managers. This would then serve as a *hint* to those
>> managers to set the desktop up accordingly.
>>
>> Of course, this is mostly for virtual hardware, since without
>> accelerometers, gyros and gps positioners on monitors, the kernel
>> wouldn't be able to know where the user put his monitors.
>>
>> One could argue that this is purely user-space policy, but since those
>> managers monitor the kms interface anyway it would be a convenient place
>> to expose this information.
>>
>> One idea would to place the x,y location in an output property.
>>
>> Another idea would be to send new layout for all connected output as a
>> drm event.
>>
> Have a look at drm-next, we added a suggested x/y property to connectors,
> and qxl support for it.
>
> I think the spice guys added mutter support for it as well and qxl
> X.org driver passes through the property.
>
> Dave.
Cool, I'll take a look.
Thanks,
Thomas
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2014-12-11 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 10:58 Exposing monitor layout to desktop managers Thomas Hellstrom
2014-12-11 11:57 ` Dave Airlie
2014-12-11 12:09 ` Thomas Hellstrom [this message]
2014-12-15 19:03 ` Thomas Hellstrom
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=54898984.1090003@shipmail.org \
--to=thomas@shipmail.org \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-graphics-maintainer@vmware.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.