Please explain the "oops", if you can.
The other poster wasn't able to point out my errors either.
TBolt peripherals are any peripheral connected via TBolt.
We simply need to agree to disagree on this one.
Someday, when it actually ships, imagine that I plug a USB mouse into an Apple TBolt Display.
If I look at the device characteristics or the PCIe map - there's no "TBolt mouse" on my system.
It shows up as a "USB mouse".
If I connect a TBolt disk enclosure, I don't see any "TBolt disks" - I see SATA disks connected to a PCIe SATA controller (or virtual disk LUNs connected to a PCIe RAID controller).
When I say that there are no TBolt devices, I mean that a remote root user on the system might not be able to tell if the system has any devices connected via TBolt. To the system, they are all devices connected through PCIe controllers - like all or almost all of the other devices on the system.
I'm still confused ... what exactly is native TB to you? Your earlier example of two mDP is what the Thunderbolt display has. As for the rest, I thought Thunderbolt was simply a fancy, long-range PCIe connection that also carries video. So what does having a PCIe driver have to do with a device not being native Thunderbolt? What would be the advantage of being "native"? My questions are in earnest. I'll admit this is not an area I know much about and your discussion is somewhat difficult to follow ...
"Native" would mean that the device directly connects to the TBolt controller, not through a TBolt -> PCIe bridge -> PCIe controller -> device.
From the system viewpoint, TBolt doesn't exist.
It passes DisplayPort signals through untouched.
It allows PCIe controllers (either slot-based or embedded) that are outside the box to be used, and devices attached to those PCIe controllers to be seen. They are seen as PCIe devices, though, not as TBolt devices.
I can't wait for someone to actually receive a TBolt device and post the PCI mapping for the system.