From: Dave Airlie <airlied@gmail.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: drm tiled monitor support (not hiding in kernel)
Date: Mon, 20 Oct 2014 16:37:10 +1000 [thread overview]
Message-ID: <1413787036-19114-1-git-send-email-airlied@gmail.com> (raw)
So I believe attempts to hide the DP MST tiled monitors in the kernel,
are a path to failure, so I've resurrected my previous code to just
create a tile property on the connectors for userspace to key off.
The contents of the tile blob are ABI, and I expect it to be
parsed by a fair few userspace projects.
So far I've ported a few pieces of GNOME to using it and posted
patches for that to their lists,
The X server should use this for make better XINERAMA info,
but otherwise drivers should pass the TILE property through
to the clients, as it contains nothing kernel specific.
Dave.
next reply other threads:[~2014-10-20 6:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 6:37 Dave Airlie [this message]
2014-10-20 6:37 ` [PATCH 1/6] drm/displayid: add displayid defines and edid extension Dave Airlie
2014-10-20 16:16 ` Jani Nikula
2014-10-20 6:37 ` [PATCH 2/6] drm: add tile_group support Dave Airlie
2014-10-20 9:11 ` David Herrmann
2014-10-20 15:32 ` Daniel Vetter
2014-10-22 2:23 ` Dave Airlie
2014-10-22 8:42 ` Daniel Vetter
2014-10-20 6:37 ` [PATCH 3/6] drm/mst: cached EDID for logical ports Dave Airlie
2014-10-20 6:37 ` [PATCH 4/6] drm/connector: store tile information from displayid Dave Airlie
2014-10-20 6:37 ` [PATCH 5/6] drm/tile: expose the tile property to userspace Dave Airlie
2014-10-20 9:15 ` David Herrmann
2014-10-20 15:31 ` Daniel Vetter
2014-10-20 15:34 ` [Intel-gfx] " Daniel Vetter
2014-10-20 15:35 ` Daniel Vetter
2014-10-20 6:37 ` [PATCH 6/6] drm/fb: add support for tiled monitor configurations Dave Airlie
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=1413787036-19114-1-git-send-email-airlied@gmail.com \
--to=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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