From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "Jamet, Michael" <michael.jamet@intel.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Levy, Amir (Jer)" <amir.jer.levy@intel.com>,
"Alloun, Dan" <dan.alloun@intel.com>,
Rafael Wysocki <rjw@rjwysocki.net>,
Andreas Noever <andreas.noever@gmail.com>
Subject: Re: [PATCH] pci: support Thunderbolt requirements for I/O resources.
Date: Mon, 24 Nov 2014 09:17:29 +0000 [thread overview]
Message-ID: <20141124091729.3de7ae7b@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <CAErSpo5z41ZOL3xUwwSZ8UE_KGmCDOUmFQ3CY_QwF7JVhU1-EQ@mail.gmail.com>
> > 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.
next prev parent reply other threads:[~2014-11-24 9:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-13 2:52 Michael Jamet
2014-11-12 17:29 ` Bjorn Helgaas
2014-11-12 18:30 ` Andy Shevchenko
2014-11-12 20:19 ` Andreas Noever
2014-11-18 8:20 ` Jamet, Michael
2014-11-18 15:47 ` Andreas Noever
2015-01-18 14:16 ` Jamet, Michael
2014-11-18 8:15 ` Jamet, Michael
2014-11-18 7:57 ` Jamet, Michael
2014-11-18 15:58 ` Bjorn Helgaas
2014-11-24 9:17 ` One Thousand Gnomes [this message]
2014-12-03 0:19 ` Bjorn Helgaas
2015-01-18 14:15 ` Jamet, Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141124091729.3de7ae7b@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=amir.jer.levy@intel.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--cc=dan.alloun@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=rjw@rjwysocki.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®