From: Yinghai Lu <yinghai@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Francois Rigaut <frigaut@gmail.com>,
linux-pci@vger.kernel.org,
Nico Schottelius <nico-linux-20120419@schottelius.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux Support for Thunderbolt using Apple Monitor
Date: Fri, 4 May 2012 12:37:19 -0700 [thread overview]
Message-ID: <CAE9FiQWuePNRWV=ncJkF57aQZ0ZT91xxZ0sZMexq8HgN9NcAfA@mail.gmail.com> (raw)
In-Reply-To: <20120504184851.GB11223@kroah.com>
On Fri, May 4, 2012 at 11:48 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> Ok, it looks like these are the devices that we are missing while
> "hotplugging":
> 37:00.0 PCI bridge: Intel Corporation Device 1513
> 38:00.0 PCI bridge: Intel Corporation Device 1513
> 38:01.0 PCI bridge: Intel Corporation Device 1513
> 38:02.0 PCI bridge: Intel Corporation Device 1513
> 38:03.0 PCI bridge: Intel Corporation Device 1513
> 38:04.0 PCI bridge: Intel Corporation Device 1513
> 38:05.0 PCI bridge: Intel Corporation Device 1513
> 39:00.0 PCI bridge: Pericom Semiconductor Device 400c (rev 02)
> 3a:03.0 PCI bridge: Pericom Semiconductor Device 400c (rev 02)
> 3b:00.0 USB controller: Pericom Semiconductor Device 400e (rev 01)
> 3b:00.1 USB controller: Pericom Semiconductor Device 400e (rev 01)
> 3b:00.2 USB controller: Pericom Semiconductor Device 400f (rev 01)
> 3c:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57761 Gigabit Ethernet PCIe (rev 10)
> 3d:00.0 FireWire (IEEE 1394): nee Agere Systems nee Lucent
> Microelectronics FW643 PCI Express 1394b Controller (PHY/Link) (rev 08)
>
> Which is good, I was worried that there was a video controller out there
> on the end of the thunderbolt link.
>
> So, the problem really is two here:
> - your video card doesn't detect the new display
> - your pci devices do not show up
>
> The first one probably needs to be reported to the Intel video driver
> people, they can help you out the best.
>
> The second one means that something is up with the pci hotplug
> controller. I've cced the linux-pci list, the people there should be
> able to help out better than I, as I no longer have any PCI hotplug
> hardware to work with anymore.
>
those devices are under 04:04.0, but that does not have slot cap
enabled by BIOS. So pciehp is going to to help.
04:04.0 PCI bridge: Intel Corporation Device 151a (rev 01) (prog-if 00
[Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 256 bytes
Bus: primary=04, secondary=37, subordinate=67, sec-latency=0
Memory behind bridge: a0900000-a09fffff
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [80] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [88] MSI: Enable+ Count=1/1 Maskable- 64bit+
Address: 00000000fee0f00c Data: 4189
Capabilities: [c0] Express (v2) Downstream Port (Slot-), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us
ExtTag+ RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #4, Speed 2.5GT/s, Width x4, ASPM L0s L1, Latency L0
unlimited, L1 unlimited
ClockPM- Surprise- LLActRep+ BwNot+
LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive-
BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- ARIFwd-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-,
Selectable De-emphasis: -6dB
Transmit Margin: Normal Operating Range, EnterModifiedCompliance-
ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-,
EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
next prev parent reply other threads:[~2012-05-04 19:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 16:38 Linux Support for Thunderbolt using Apple Monitor Nico Schottelius
2012-04-19 21:15 ` Greg KH
[not found] ` <CAMVeQ8r_3vuAxzbLyKoecOHOOGijUDkLfw+MK7o-WoWbuOGSrg@mail.gmail.com>
2012-05-02 16:36 ` Nico Schottelius
2012-05-02 20:25 ` Greg KH
2012-05-03 6:50 ` Nico Schottelius
2012-05-03 15:34 ` Greg KH
[not found] ` <CAMVeQ8qYu4bShd_+pwRv8bShhusJMDa-jjoqu7EujS4jt7RSNA@mail.gmail.com>
2012-05-03 15:35 ` Greg KH
2012-05-03 18:40 ` Nico Schottelius
2012-05-03 18:51 ` Greg KH
[not found] ` <CAMVeQ8q3PMMGmFSgrnqbW2HVdfmN+LgatX3TSfv5_2Ebuuj=QQ@mail.gmail.com>
2012-05-03 23:38 ` Greg KH
2012-05-04 4:19 ` Francois Rigaut
2012-05-04 18:48 ` Greg KH
2012-05-04 19:37 ` Yinghai Lu [this message]
2012-05-04 19:38 ` Yinghai Lu
2012-05-05 4:19 ` Francois Rigaut
2012-05-05 8:18 ` Jiang Liu
2012-05-05 8:47 ` Francois Rigaut
2012-05-05 15:27 ` Jiang Liu
2012-05-05 15:18 ` Jiang Liu
2012-05-05 16:48 ` Nico Schottelius
2012-05-06 3:22 ` Jiang Liu
2012-05-09 16:05 ` Greg KH
2012-05-10 1:49 ` Francois Rigaut
2012-05-10 3:45 ` Greg KH
2012-05-06 3:59 ` Francois Rigaut
2012-05-05 0:28 ` Francois Rigaut
2012-05-05 0:35 ` Greg KH
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='CAE9FiQWuePNRWV=ncJkF57aQZ0ZT91xxZ0sZMexq8HgN9NcAfA@mail.gmail.com' \
--to=yinghai@kernel.org \
--cc=frigaut@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nico-linux-20120419@schottelius.org \
/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;
as well as URLs for NNTP newsgroup(s).