From: "Duff O'Melia" <duff@omelia.org>
To: "Mika Westerberg" <mika.westerberg@linux.intel.com>
Cc: westeri@kernel.org, andreas.noever@gmail.com,
YehezkelShB@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, imre.deak@intel.com
Subject: Re: [RFC PATCH] thunderbolt: Tunnel only the first DP OUT of Apple Studio Displays
Date: Thu, 12 Nov 2026 17:38:46 -0500 [thread overview]
Message-ID: <82a62e13-928a-4973-b88f-ea2642132fc1@app.fastmail.com> (raw)
In-Reply-To: <20261109103039.GK176724@black.igk.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Hi Mika,
On Mon, Nov 09, 2026 at 11:30:39AM +0100, Mika Westerberg wrote:
> Can you provide full dmesg with thunderbolt.dyndbg=+p and drm.debug=0x10e
> in the kernel command line when you have everything connected and the issue
> reproduces?
Sure, it's attached, xz-compressed. It's from a reboot with everything
connected, on Omarchy's 7.2.15 kernel with its stock Thunderbolt driver
(my patch not applied). I added log_buf_len=64M so the start of the boot
isn't lost. I removed MAC addresses, USB serial numbers and some
firewall log lines, and changed nothing else.
In short:
- 0-3 is the 2026 model (0x8025). Both of its DP OUT adapters got
tunneled: 0:5 <-> 3:11 and 0:10 <-> 3:12.
- 1-1 is a 2022 model (0x801f) on the second host router. It got
0:6 <-> 1:10.
- 0-1 is the other 2022 model. It came up last, found no free DP IN
adapter ("no suitable DP IN adapter available, not tunneling") and
stays dark.
- In xe, DP-1 (DPTUN 0:1:5) is the 2026 model's first tile, DP-3
(DPTUN 0:1:10) its second tile, and DP-2 (DPTUN 1:1:6) the 2022
model. DP-1 and DP-2 run at 5120x2880.
One correction to my patch description: on this boot DP-3 isn't
disabled. Pipe D is active on it at 2560x2880 with no framebuffer on its
primary plane, and the compositor doesn't list it as a monitor. So the
second tile's stream does come up, but it shows nothing.
I'm happy to run anything else, such as the same boot with the patch
applied for comparison.
Thanks,
Duff
[-- Attachment #2: dmesg-stock-driver-2026-11-12.txt.xz --]
[-- Type: application/x-xz, Size: 99520 bytes --]
prev parent reply other threads:[~2026-11-12 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 15:44 Duff OMelia
2026-11-09 10:30 ` Mika Westerberg
2026-11-12 22:38 ` Duff O'Melia [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=82a62e13-928a-4973-b88f-ea2642132fc1@app.fastmail.com \
--to=duff@omelia.org \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=imre.deak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=westeri@kernel.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
all inboxes | Powered by JetHome®