From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Brad Campbell <lists2009@fnarfbargle.com>
Cc: linux-kernel@vger.kernel.org, michael.jamet@intel.com,
YehezkelShB@gmail.com
Subject: Re: Thunderbolt DP oddity on v5.2.9 on iMac 12,2
Date: Wed, 28 Aug 2019 16:19:43 +0300 [thread overview]
Message-ID: <20190828131943.GZ3177@lahna.fi.intel.com> (raw)
In-Reply-To: <e3a8fa91-2cfd-76a4-641c-610c32122833@fnarfbargle.com>
On Wed, Aug 28, 2019 at 06:43:35PM +0800, Brad Campbell wrote:
> On 28/8/19 6:23 pm, Mika Westerberg wrote:
>
> > On Wed, Aug 28, 2019 at 05:12:00PM +0800, Brad Campbell wrote:
> >
> > Apart from the warning in the log (which is not fatal, I'll look into
> > it) to me the second path setup looks fine.
> >
> > Can you do one more experiment? Boot the system up without anything
> > connected and then plug both monitors. Does it work?
> >
>
> Aside from head ordering issues in X it works just fine.
> I've attached the dmesg. Boot with nothing plugged in, then plug in 0-1 and
> 0-3 in that order.
OK, thanks for checking. So when Linux is in complete control both DP
tunnels get created properly. I suspect there is something different
what the firmware does compared to other Macs I've been using and that
causes the driver to fail to discover all the paths. I will take a look
at this but I'm away tomorrow and friday so it goes to next week.
BTW, have you tried to chain the two monitors?
next prev parent reply other threads:[~2019-08-28 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 7:09 Brad Campbell
2019-08-28 7:33 ` Mika Westerberg
2019-08-28 9:12 ` Brad Campbell
2019-08-28 9:34 ` Brad Campbell
2019-08-28 10:23 ` Mika Westerberg
2019-08-28 10:43 ` Brad Campbell
2019-08-28 13:19 ` Mika Westerberg [this message]
2019-08-28 16:27 ` Brad Campbell
2019-09-03 10:13 ` Mika Westerberg
2019-09-03 10:36 ` Mika Westerberg
2019-09-03 11:11 ` Brad Campbell
2019-09-03 11:55 ` Mika Westerberg
2019-09-03 12:54 ` Brad Campbell
2019-09-03 13:33 ` Mika Westerberg
2019-09-13 8:24 ` Mika Westerberg
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=20190828131943.GZ3177@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists2009@fnarfbargle.com \
--cc=michael.jamet@intel.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
all inboxes | Powered by JetHome®