From: "\"Kristóf, Csillag\"" <csillag.kristof@gmail.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Question about driver capatibilities - triple monitor?
Date: Wed, 23 Jan 2013 12:41:44 +0100 [thread overview]
Message-ID: <50FFCC78.20209@gmail.com> (raw)
In-Reply-To: <kdlc26$use$1@ger.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1962 bytes --]
At 2013-01-22 07:36, Ian Pilcher wrote:
> On 01/21/2013 06:05 PM, Csillag wrote:
>> But now, thanks to GIGABYTE's PR about Thunderbolt and 4K (
>> http://www.gigabyte.com/MicroSite/323/4k.html ), I realized that it
>> might be possible to use a "DisplayPort to Dual-DisplayPort Adapter" to
>> split a DisplayPort 1.1 output into two channels, and drive two monitors
>> from there. (Of course the resolution is limited, but 1920 x 1200 is
>> just what I need.)
> Be careful. When I looked into those "splitters", I found out that
> they are closer to "federators". In other words, they take 2 displays
> and make them looks like 1 giant display to the operating system.
>
> So 2 1920x1200 displays would appear to be a single 3840x1200 display.
>
> This will give you the number of pixels that you expect, but your
> desktop environment is unlikely to play all that well with such a
> configuration.
That's not necessarily a problem.
I had good results with the fakeXinerama library earlier.
You divert Xorg's Xinerama library with this library, feed it a text
config file, describing what you want,
and then all X client applications that ask about the monitor layout
(like window managers) get this data.
With this, one can make any big monitor appear like several devices.
(And then you can maximize windows to the separated areas, etc.)
Of course you won't be able to use xrandr to configure the layout of the
devices, but if all you want is one constant resolution, and the devices
are placed in the proper order & orientation, this should not be a problem.
* * *
I am more worried about the internals of this "federating" implementation.
Do I have to connect identical monitors, or identical resolution &
frequency is enough?
(For example, would two different Samsung 1920x1200 @ 60 displays work?)
> (If anyone knows of a device that doesn't operate this way, please let
> me know. I'll almost certainly buy a couple.)
+1
Kristof
[-- Attachment #1.2: Type: text/html, Size: 3407 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2013-01-23 11:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 0:05 Question about driver capatibilities - triple monitor? Csillag
2013-01-22 6:36 ` Ian Pilcher
2013-01-22 8:43 ` Daniel Vetter
2013-01-23 11:46 ` "Kristóf, Csillag"
2013-01-23 12:02 ` Daniel Vetter
2013-01-24 18:46 ` Monitors on thunderbolt? (Was: Question about driver capatibilities - triple monitor?) "Kristóf, Csillag"
2013-01-25 21:56 ` Question about driver capatibilities - triple monitor? "Kristóf, Csillag"
2013-01-23 11:41 ` "Kristóf, Csillag" [this message]
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=50FFCC78.20209@gmail.com \
--to=csillag.kristof@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).