linux-kernel - Re: Linux Support for Thunderbolt using Apple Monitor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120503065003.GB13386@schottelius.org>
Date:	Thu, 3 May 2012 08:50:03 +0200
From:	Nico Schottelius <nico-linux-20120419@...ottelius.org>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	Nico Schottelius <nico-linux-20120419@...ottelius.org>,
	Francois Rigaut <frigaut@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Linux Support for Thunderbolt using Apple Monitor

Greg KH [Wed, May 02, 2012 at 01:25:09PM -0700]:
> Thunderbolt should show up to the kernel just as a "normal" PCIE link,
> so there shouldn't be anything special we need to do to handle this at
> all (or at least my Intel contacts said that.)

Well, at least from my lspci point of view (before/after disconnect same
output), this seems to be wrong (no dmesg output as well).

Additionally as far as I understand
thunderbolt, it's bundling display port and pci-e into a single channel,
so I'm not sure if this is 100% transparent pci-e + displayport from our
side.

Or, the better question is probably: How should Linux realise that there
is a change (apple monitor with ethernet, usb, co. plugged in) going on?

> Note, I haven't tested this yet, so I can't verify it, but if you have
> the hardware, you should be able to.

I can test stuff here, but would be thankful for a round of pointers on
how to debug / approach this.

Cheers,

Nico

-- 
PGP key: 7ED9 F7D3 6B10 81D7 0EC5  5C09 D7DC C8E4 3187 7DF0
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/