... lol I tested your thunderbolt implementation with SSDT-TB3-9560.aml (having also SSDT-TYPC-9560 in patched folder) using my hackbook connected via thunderbolt to my Dell Latitude 7490 windows 10 laptop (see post above). I also deactivated all TB security options in both laptop bios to be sure no issue could come from this.
First, TB3 hotplug is detected in the Device tree! It is seen as a PCI device with the KNNSpeed PCI card trick. (see attached IOreg)
But wait, hold your breath: I said detected, not that it works - sorry lol
Whenever I removed the thunderbolt cable, I always have an instant kernel panic (KP report attached here).
View attachment 409773
View attachment 409775
In windows, my hackbook is also detected as a Thunderbolt device:
View attachment 409776
But normally it should be detected as a Thunderbolt Ethernet device (using the example in the above post, windows laptop connected via TB3 to hackbook).
Here, we only see "something" connected as "Port 1" but in windows prefs, no ethernet device is showing.
So we can conclude that Thunderbolt ethernet isn't working here.
But still, when windows doesn't detect any TB ethernet device nor the hackbook on the local network, the hack will detect the PC on the local network ?!
View attachment 409781
On the other hand, surprisingly Thunderbolt Cold plug doesn't work at all
. Whether cold booted or after reboot, no single device will appear in the tree, no PCI card icon either.
Another observation. I tried to plug my cheap TYP-C/TB adapter with a USB3 dongle connected + the same setup above connecting the TB port on the adapter to windows laptop via TB3. Here, nothing is showing in the device tree and naturally I don't have any Kernel Panic if I unplug the TB cables. Last, windows laptop acts here as if my hackbook was delivering power over TB, but showing an error message "your adapter doesn't deliver enough power", something like that.
EDIT: this is a USB-C power port not a thunderbolt pass-through port (facepalm me, I've been fooled by the apparent lighting symbol - definitely not TB lol).
So that's it for tonight, tomorrow I will test it with original KNNSpeed TYPCSSDT to compare the differences.
Last question: what's the cheapest TB3 device (more common than daisy-chaining 2 laptops lol) money can buy, so we can continue testing? NVME TB3 enclosures costs an arm, eGPU the same... just can't afford it nor have the need for it.
I thought about using an original apple Thunderbolt to Ethernet adapter but my guess is that the hack will see it as a USB Type-C to Ethernet adapter instead. I found a second hand Dell TB16 thunderbolt dock for 50$ on Craigslist (same as @auguzanellato
), but again without any TB device connected to it I doubt I will see anything relevant regarding TB3.
NB: I am in a dual boot environment on the same SSD, having installed TB drivers/firmware for windows. I don't think it has any influence in these tests but I mention this because I've seen others like @kgp
who managed to get it work (on desktop though, using another method) having installed these drivers on windows to succeed in OSX.