From: Brad Campbell <lists2009@fnarfbargle.com>
To: Mika Westerberg <mika.westerberg@linux.intel.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: Thu, 29 Aug 2019 00:27:08 +0800 [thread overview]
Message-ID: <be32b369-b013-cca8-5475-9b56acaa3e18@fnarfbargle.com> (raw)
In-Reply-To: <20190828131943.GZ3177@lahna.fi.intel.com>
On 28/8/19 21:19, Mika Westerberg wrote:
> 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.
It wouldn't surprise me if the firmware was doing something funky. It
was one of the first Thunderbolt equipped models and the support docs
explicitly say only one Thunderbolt display in Windows and two in later
versions of OSX. It almost needs a quirk to say "firmware does something
we don't like, reset the controller and re-discover from scratch".
Anyway, I'm not in any hurry. It doesn't get rebooted often and it's not
in any way preventing me using the machine. In fact, upgrading the third
head from an old 24" 1920x1200 to the second Thunderbolt display has
been invaluable.
> BTW, have you tried to chain the two monitors?
Not yet, but it was something I've been considering. I'll give it a go
tomorrow. Due to cable length vs display dimensions it'll require me
cleaning my desk, and that takes some forward planning.
--
An expert is a person who has found out by his own painful
experience all the mistakes that one can make in a very
narrow field. - Niels Bohr
next prev parent reply other threads:[~2019-08-28 16:27 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
2019-08-28 16:27 ` Brad Campbell [this message]
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=be32b369-b013-cca8-5475-9b56acaa3e18@fnarfbargle.com \
--to=lists2009@fnarfbargle.com \
--cc=YehezkelShB@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@linux.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®