linux-kernel - Re: [PATCH] pci: support Thunderbolt requirements for I/O resources.

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 24 Nov 2014 09:17:29 +0000
From:	One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	"Jamet, Michael" <michael.jamet@...el.com>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Levy, Amir (Jer)" <amir.jer.levy@...el.com>,
	"Alloun, Dan" <dan.alloun@...el.com>,
	Rafael Wysocki <rjw@...ysocki.net>,
	Andreas Noever <andreas.noever@...il.com>
Subject: Re: [PATCH] pci: support Thunderbolt requirements for I/O
 resources.

> > 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 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/