All of lore.kernel.org
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, xorg-devel@lists.x.org
Subject: Re: intel driver 4k MST
Date: Mon, 27 Mar 2017 17:40:33 +0200	[thread overview]
Message-ID: <95E76545-8F28-454D-986A-459701FE193F@exactcode.com> (raw)
In-Reply-To: <20170327152650.GX10606@nuc-i3427.alporthouse.com>

Hi,

On Mar 27, 2017, at 17:26, Chris Wilson <chris@chris-wilson.co.uk> wrote:

> On Mon, Mar 27, 2017 at 04:47:44PM +0200, René Rebe wrote:
>> Hi all,
>> 
>> connecting a Dell 4k MST display using the xorg intel driver on two different machines (Surface Pro 3, Dell XPS 13 9360) results in one of the two halts mirrored on the two MST halfs of the display. Using xrandr --left-of / --right-of I could not yet find a combination that would correctly show the whole screen.
>> 
>> In contrast using the xorg modesetting driver on the same kernel and xorg-server 4k MST works out of the box.
>> 
>> Is this a know limitation or the intel xorg driver that is just considered obsolete and dead or anything?
> 
> It is not likely a ddx bug...

Meaning? MST works correcting when using the xorg mode setting driver, … so the kernel side should be ok, no?

How to move forward? Is the xorg intel driver despite missing releases under active development, or should I just use the lower performance mode setting driver?

Interested in any debug output? The display is a Dell UltraSharp 24″ 4K UP2414Q.

	René

-- 
 ExactCODE GmbH, Lietzenburger Str. 42, DE-10789 Berlin
 http://exactcode.com | http://exactscan.com | http://ocrkit.com | http://t2-project.org | http://rene.rebe.de

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-03-27 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27 14:47 intel driver 4k MST René Rebe
     [not found] ` <BFA157E2-465B-4D8C-B82D-C80CD6766D07-mWpqEAMA8ohl57MIdRCFDg@public.gmane.org>
2017-03-27 15:26   ` [Intel-gfx] " Chris Wilson
2017-03-27 15:40     ` René Rebe [this message]
2017-03-27 18:36       ` Jani Nikula

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=95E76545-8F28-454D-986A-459701FE193F@exactcode.com \
    --to=rene@exactcode.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=xorg-devel@lists.x.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 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.