Re: Linux Support for Thunderbolt using Apple Monitor

[Yinghai Lu]

On Fri, May 4, 2012 at 11:48 AM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> 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-
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/