Originally posted by uid313
View Post
Announcement
Collapse
No announcement yet.
Thunderbolt Networking Support Is Still Being Worked On For Linux
Collapse
X
-
Originally posted by schmidtbag View PostI really don't understand why Intel has let Thunderbolt continue for as long as they have, especially since it competes with their own technologies (like USB).
There are hardly any compatible devices worth considering, it has been littered with problems in both Mac and Windows,
and the hardware evolves so quickly that it isn't really worth buying anything for it. Also, it seems to be less common than eSATA, which is saying a lot. It had some interesting potential,
with things like external GPUs or daisy chaining a single cable for all external devices. But that stuff just didn't take off.
Thunderbolt is effectively the successor to Firewire, and somehow Intel didn't realize that Firewire died off because nobody cared about it.
- Likes 1
Comment
-
Originally posted by uid313 View Post
I thought a tablet would be more likely to have a USB port than a Thunderbolt port.
Most tablets are ARM and I don't think there is any Thunderbolt-equipped ARM device.
Most smartphones and tablets seems to heading toward USB Type-C.
Comment
-
My new Clevo laptop (P751DM) has a Thunderbolt 3/USB 3.1 combo port. Currently, I have neither TB3 nor USB 3.1 device to test with, but I wonder what it should look like in dmesg/lspci/lsusb. I don't know what to look for, and I have no idea about the name of the hardware implementing this combo. If someone has a hint, I'm interested.
At the moment (kernel 4.6), the only difference I could notice by disabling/enabling TB3 was an extra PCI bridge, but I don't know if it's enough to prove some TB3 support. And for USB 3.1, no sign of 3.1 anywhere.
Comment
-
Originally posted by totoz View PostMy new Clevo laptop (P751DM) has a Thunderbolt 3/USB 3.1 combo port. Currently, I have neither TB3 nor USB 3.1 device to test with, but I wonder what it should look like in dmesg/lspci/lsusb. I don't know what to look for, and I have no idea about the name of the hardware implementing this combo. If someone has a hint, I'm interested.
At the moment (kernel 4.6), the only difference I could notice by disabling/enabling TB3 was an extra PCI bridge, but I don't know if it's enough to prove some TB3 support. And for USB 3.1, no sign of 3.1 anywhere.
If they don't show up you probably lack drivers for themso they aren't even initialized/recognized.
If you want to post the output here I can have a look and see if something looks like them. Just redact the MAC addresses from the ethernet entries if you post here the full dump.
Comment
-
Originally posted by starshipeleven View PostThe ethernet controller has DMA, direct memory access.
Whatever is connected to ethernet cable does not have DMA and can only talk to the ethernet controller.
Any kind of communication that does not broadly resemble ethernet can't get past the ethernet controller as it won't understand it.
Thunderbolt has pcie lines, and pcie lines allow ANYTHING you connect to them (an external port) to have DMA.
So yeah, it's not the same thing at all.
However, where Thunderbolt is used as a system interconnection (IPoTB supported on OS X Mavericks), then the IP implementation runs on the underlying Thunderbolt low-latency packet-switching fabric, and the PCI Express protocol is not present on the cable. That means that if IPoTB networking is used between a group of computers, there is no threat of such DMA attack between them.
Comment
-
My point was that thunderbolt allows pcie lines and thus DMA to be accessed from an external port.
Of course while the cable is in use to do something else that does not involve using pcie lanes (like also the displayport function or the USB 3.0 one), the pcie lines are not used thus there is no risk of DMA.
Point is, how do you tell that a device using a Thunderbolt port isn't malicious (i.e. using pcie lanes to do bad things too)? You break out your hardware logic analyzers and sniff the communication?
Comment
-
Originally posted by wizard69 View PostTB was never meant to compete with USB. It is an entirely different technology solving different technical issues.
And USB hasn't? Frankly it took a long time for the first rounds of USB chips to evolve to the point of working correctly. This especially with USB 3 chips as many of the early ones where very buggy.
It still has a lot of potential and frankly is being implemented in many applications where it makes sense. USB3 / TB will only take it further as the special external hardware is eliminated.
The idea of external GPU's is some idiots pipe dream. To put it bluntly it doesn't make any economic sense. There are rumors of Apple integrating a GPU into a video monitor but even that will likely blow out the cost of the monitor to the point it Never becomes popular.Last edited by schmidtbag; 15 July 2016, 09:26 AM.
Comment
-
Originally posted by starshipeleven View PostAny controller of USB and thunderbolt should show up with lshw run as root, as that should print all hardware info.
If they don't show up you probably lack drivers for themso they aren't even initialized/recognized.
If you want to post the output here I can have a look and see if something looks like them. Just redact the MAC addresses from the ethernet entries if you post here the full dump.
Comment
-
Originally posted by totoz View PostHere it is: http://pastebin.com/1tKNdx2L
Looking around, it seems that another guy with a skylake thunderbolt system can see the thunderbolt in linux ONLY if at boot there is something connected to the thunderbolt port https://bugzilla.kernel.org/show_bug.cgi?id=115121
If you look at his "lspci-connected-at-boot.log"
you see the last entry (not present in the other log)
"06:00.0 PCI bridge: Intel Corporation Device 1576 (prog-if 00 [Normal decode])"
the device "1576" happens to be a thunderbolt controller, "DSL6340 Thunderbolt 3 Bridge [Alpine Ridge 2C 2015]" https://pci-ids.ucw.cz/read/PC/8086
Comment
Comment