> > This was also discussed internally and the only way to identify Thunderbolt > > devices is to check the device IDs. > > As you said, this will require us to maintain and keep the list up-to-date > > as we deliver new devices. > > I don't really see how this can work. You're asking me to put changes > based on a secret spec into generic code that is used on every machine > with PCI. I have no way to maintain something like that.
> > This seems like a major screw up in the design and documentation of > Thunderbolt. See https://developer.apple.com/library/mac/documentation/HardwareDrivers/Conceptual/ThunderboltDevGuide/ThunderboltDevGuide.pdf page 10 for one of the brief public notes on the not relying on I/O space. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
