* PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! @ 2009-09-29 18:23 Stefani Seibold 2009-09-29 23:15 ` Rafael J. Wysocki 0 siblings, 1 reply; 7+ messages in thread From: Stefani Seibold @ 2009-09-29 18:23 UTC (permalink / raw) To: linux-kernel Hi PCI Hackers, i have trouble with an ExpressCard PCI Express-to-PCI Bridge manufactured by DUEL System under X86/32 Linux kernel 2.6.31. The kernel will recognized the Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge and the attached Texas Instruments PCIxx12 Cardbus Controller, but the yenta socket driver will fail with the message: yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses') The output of dmesg looks like: pci 0000:0e:00.0: supports D1 D2 pci 0000:0f:00.0: reg 10 32bit mmio: [0x000000-0x000fff] pci 0000:0f:00.0: supports D1 D2 pci 0000:0f:00.0: PME# supported from D0 D1 D2 D3hot D3cold pci 0000:0f:00.0: PME# disabled pci 0000:0e:00.0: bridge io port: [0x00-0xfff] pci 0000:0e:00.0: bridge 32bit mmio: [0x000000-0x0fffff] pci 0000:0e:00.0: bridge 64bit mmio pref: [0x000000-0x0fffff] pci 0000:0e:00.0: PCI bridge, secondary bus 0000:0f pci 0000:0e:00.0: IO window: disabled pci 0000:0e:00.0: MEM window: 0xf1c00000-0xf1cfffff pci 0000:0e:00.0: PREFETCH window: disabled decode_hpp: Could not get hotplug parameters. Use defaults pci 0000:0e:00.0: enabling device (0000 -> 0002) pci 0000:0e:00.0: setting latency timer to 64 yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses') lspci -v shows: 0e:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03) (prog-if 00 [Normal decode]) Physical Slot: 1 Flags: bus master, fast devsel, latency 0 Bus: primary=0e, secondary=0f, subordinate=0f, sec-latency=64 Memory behind bridge: f1c00000-f1cfffff Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+ Capabilities: [80] Subsystem: Device 5678:1234 Capabilities: [90] Express PCI/PCI-X Bridge, MSI 00 Capabilities: [100] Advanced Error Reporting 0f:00.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller Subsystem: Texas Instruments Device ac48 Flags: medium devsel, IRQ 255 Memory at f1c00000 (32-bit, non-prefetchable) [disabled] [size=4K] Bus: primary=00, secondary=00, subordinate=00, sec-latency=0 I/O window 0: 00000000-00000003 [disabled] I/O window 1: 00000000-00000003 [disabled] 16-bit legacy interface ports at 0001 Any idea where the problem is located or how can i fix it? If you need further information or dumps please contact me. Stefani ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! 2009-09-29 18:23 PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! Stefani Seibold @ 2009-09-29 23:15 ` Rafael J. Wysocki 2009-10-24 14:03 ` Stefani Seibold 0 siblings, 1 reply; 7+ messages in thread From: Rafael J. Wysocki @ 2009-09-29 23:15 UTC (permalink / raw) To: Stefani Seibold; +Cc: linux-kernel, Linux PCI, Jesse Barnes [Adding CCs.] On Tuesday 29 September 2009, Stefani Seibold wrote: > Hi PCI Hackers, > > i have trouble with an ExpressCard PCI Express-to-PCI Bridge > manufactured by DUEL System under X86/32 Linux kernel 2.6.31. > > The kernel will recognized the Texas Instruments XIO2000(A)/XIO2200(A) > PCI Express-to-PCI Bridge and the attached Texas Instruments PCIxx12 > Cardbus Controller, but the yenta socket driver will fail with the > message: > > yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses') > > The output of dmesg looks like: > > pci 0000:0e:00.0: supports D1 D2 > pci 0000:0f:00.0: reg 10 32bit mmio: [0x000000-0x000fff] > pci 0000:0f:00.0: supports D1 D2 > pci 0000:0f:00.0: PME# supported from D0 D1 D2 D3hot D3cold > pci 0000:0f:00.0: PME# disabled > pci 0000:0e:00.0: bridge io port: [0x00-0xfff] > pci 0000:0e:00.0: bridge 32bit mmio: [0x000000-0x0fffff] > pci 0000:0e:00.0: bridge 64bit mmio pref: [0x000000-0x0fffff] > pci 0000:0e:00.0: PCI bridge, secondary bus 0000:0f > pci 0000:0e:00.0: IO window: disabled > pci 0000:0e:00.0: MEM window: 0xf1c00000-0xf1cfffff > pci 0000:0e:00.0: PREFETCH window: disabled > decode_hpp: Could not get hotplug parameters. Use defaults > pci 0000:0e:00.0: enabling device (0000 -> 0002) > pci 0000:0e:00.0: setting latency timer to 64 > yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses') > > lspci -v shows: > > 0e:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03) (prog-if 00 [Normal decode]) > Physical Slot: 1 > Flags: bus master, fast devsel, latency 0 > Bus: primary=0e, secondary=0f, subordinate=0f, sec-latency=64 > Memory behind bridge: f1c00000-f1cfffff > Capabilities: [50] Power Management version 2 > Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+ > Capabilities: [80] Subsystem: Device 5678:1234 > Capabilities: [90] Express PCI/PCI-X Bridge, MSI 00 > Capabilities: [100] Advanced Error Reporting > > 0f:00.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller > Subsystem: Texas Instruments Device ac48 > Flags: medium devsel, IRQ 255 > Memory at f1c00000 (32-bit, non-prefetchable) [disabled] [size=4K] > Bus: primary=00, secondary=00, subordinate=00, sec-latency=0 > I/O window 0: 00000000-00000003 [disabled] > I/O window 1: 00000000-00000003 [disabled] > 16-bit legacy interface ports at 0001 > > > Any idea where the problem is located or how can i fix it? > > If you need further information or dumps please contact me. ^ permalink raw reply [flat|nested] 7+ messages in thread
* PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! 2009-09-29 23:15 ` Rafael J. Wysocki @ 2009-10-24 14:03 ` Stefani Seibold 2009-10-24 20:34 ` Matthew Wilcox 0 siblings, 1 reply; 7+ messages in thread From: Stefani Seibold @ 2009-10-24 14:03 UTC (permalink / raw) To: linux-kernel, Linux PCI, Jesse Barnes, Rafael J. Wysocki Hi PCI Hackers, since i get no answer, it try to post my problem again. I have trouble with an ExpressCard PCI Express-to-PCI Bridge manufactured by DUEL System under X86/32 Linux kernel 2.6.31. The kernel will recognized the Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge and the attached Texas Instruments PCIxx12 Cardbus Controller, but the yenta socket driver will fail with the message: yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses') The output of dmesg looks like: pci 0000:0e:00.0: supports D1 D2 pci 0000:0f:00.0: reg 10 32bit mmio: [0x000000-0x000fff] pci 0000:0f:00.0: supports D1 D2 pci 0000:0f:00.0: PME# supported from D0 D1 D2 D3hot D3cold pci 0000:0f:00.0: PME# disabled pci 0000:0e:00.0: bridge io port: [0x00-0xfff] pci 0000:0e:00.0: bridge 32bit mmio: [0x000000-0x0fffff] pci 0000:0e:00.0: bridge 64bit mmio pref: [0x000000-0x0fffff] pci 0000:0e:00.0: PCI bridge, secondary bus 0000:0f pci 0000:0e:00.0: IO window: disabled pci 0000:0e:00.0: MEM window: 0xf1c00000-0xf1cfffff pci 0000:0e:00.0: PREFETCH window: disabled decode_hpp: Could not get hotplug parameters. Use defaults pci 0000:0e:00.0: enabling device (0000 -> 0002) pci 0000:0e:00.0: setting latency timer to 64 yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses') lspci -v shows: 0e:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03) (prog-if 00 [Normal decode]) Physical Slot: 1 Flags: bus master, fast devsel, latency 0 Bus: primary=0e, secondary=0f, subordinate=0f, sec-latency=64 Memory behind bridge: f1c00000-f1cfffff Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+ Capabilities: [80] Subsystem: Device 5678:1234 Capabilities: [90] Express PCI/PCI-X Bridge, MSI 00 Capabilities: [100] Advanced Error Reporting 0f:00.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller Subsystem: Texas Instruments Device ac48 Flags: medium devsel, IRQ 255 Memory at f1c00000 (32-bit, non-prefetchable) [disabled] [size=4K] Bus: primary=00, secondary=00, subordinate=00, sec-latency=0 I/O window 0: 00000000-00000003 [disabled] I/O window 1: 00000000-00000003 [disabled] 16-bit legacy interface ports at 0001 Any idea where the problem is located or how can i fix it? If you need further information or dumps please contact me. The kernel parameter 'pci=assign-busses' did not fix the problem. Stefani ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! 2009-10-24 14:03 ` Stefani Seibold @ 2009-10-24 20:34 ` Matthew Wilcox 2009-10-25 8:10 ` Stefani Seibold 0 siblings, 1 reply; 7+ messages in thread From: Matthew Wilcox @ 2009-10-24 20:34 UTC (permalink / raw) To: Stefani Seibold; +Cc: linux-kernel, Linux PCI, Jesse Barnes, Rafael J. Wysocki On Sat, Oct 24, 2009 at 04:03:23PM +0200, Stefani Seibold wrote: > If you need further information or dumps please contact me. > > The kernel parameter 'pci=assign-busses' did not fix the problem. What does dmesg say when you specify pci=assign-busses? -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! 2009-10-24 20:34 ` Matthew Wilcox @ 2009-10-25 8:10 ` Stefani Seibold 2009-10-25 8:38 ` Dominik Brodowski 0 siblings, 1 reply; 7+ messages in thread From: Stefani Seibold @ 2009-10-25 8:10 UTC (permalink / raw) To: Matthew Wilcox; +Cc: linux-kernel, Linux PCI, Jesse Barnes, Rafael J. Wysocki Am Samstag, den 24.10.2009, 14:34 -0600 schrieb Matthew Wilcox: > On Sat, Oct 24, 2009 at 04:03:23PM +0200, Stefani Seibold wrote: > > If you need further information or dumps please contact me. > > > > The kernel parameter 'pci=assign-busses' did not fix the problem. > > What does dmesg say when you specify pci=assign-busses? > Okay, i tried it again with 'pci=assign-bussed'. All i get is a decode_hpp: Could not get hotplug parameters. Use defaults thats all. The express-card will not be detected. ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! 2009-10-25 8:10 ` Stefani Seibold @ 2009-10-25 8:38 ` Dominik Brodowski 2009-10-26 7:27 ` Stefani Seibold 0 siblings, 1 reply; 7+ messages in thread From: Dominik Brodowski @ 2009-10-25 8:38 UTC (permalink / raw) To: Stefani Seibold Cc: Matthew Wilcox, linux-kernel, Linux PCI, Jesse Barnes, Rafael J. Wysocki Hey, On Sun, Oct 25, 2009 at 09:10:29AM +0100, Stefani Seibold wrote: > Am Samstag, den 24.10.2009, 14:34 -0600 schrieb Matthew Wilcox: > > On Sat, Oct 24, 2009 at 04:03:23PM +0200, Stefani Seibold wrote: > > > If you need further information or dumps please contact me. > > > > > > The kernel parameter 'pci=assign-busses' did not fix the problem. > > > > What does dmesg say when you specify pci=assign-busses? > > > > Okay, i tried it again with 'pci=assign-bussed'. All i get is a > > decode_hpp: Could not get hotplug parameters. Use defaults > > thats all. The express-card will not be detected. I assume the "d" at the end was just a typo -- and "lspci -vvv" looks the same? Best, Dominik ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! 2009-10-25 8:38 ` Dominik Brodowski @ 2009-10-26 7:27 ` Stefani Seibold 0 siblings, 0 replies; 7+ messages in thread From: Stefani Seibold @ 2009-10-26 7:27 UTC (permalink / raw) To: Dominik Brodowski Cc: Matthew Wilcox, linux-kernel, Linux PCI, Jesse Barnes, Rafael J. Wysocki > > > > Okay, i tried it again with 'pci=assign-bussed'. All i get is a > > > > decode_hpp: Could not get hotplug parameters. Use defaults > > > > thats all. The express-card will not be detected. > > I assume the "d" at the end was just a typo -- and "lspci -vvv" looks the > same? > Yes, this was a typo. Here are the diff's of dmesg and lspci -vvv with and without "pci=assign-busses" after inserting the express card. dmesg without 'pci=assign-busses': ---------------------------------- pci 0000:0e:00.0: supports D1 D2 pci 0000:0f:00.0: reg 10 32bit mmio: [0x000000-0x000fff] pci 0000:0f:00.0: supports D1 D2 pci 0000:0f:00.0: PME# supported from D0 D1 D2 D3hot D3cold pci 0000:0f:00.0: PME# disabled pci 0000:0e:00.0: bridge io port: [0x00-0xfff] pci 0000:0e:00.0: bridge 32bit mmio: [0x000000-0x0fffff] pci 0000:0e:00.0: bridge 64bit mmio pref: [0x000000-0x0fffff] ACPI: Delete PCI Interrupt Routing Table for 0000:0f pci 0000:0e:00.0: PCI bridge, secondary bus 0000:0f pci 0000:0e:00.0: IO window: disabled pci 0000:0e:00.0: MEM window: 0xf1c00000-0xf1cfffff pci 0000:0e:00.0: PREFETCH window: disabled decode_hpp: Could not get hotplug parameters. Use defaults pci 0000:0e:00.0: enabling device (0000 -> 0002) pci 0000:0e:00.0: setting latency timer to 64 yenta_cardbus 0000:0f:00.0: no bus associated! (try 'pci=assign-busses') CE: hpet increasing min_delta_ns to 50624 nsec lspci -vvv without 'pci=assign-busses': --------------------------------------- 0e:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03) (prog-if 00 [Normal decode]) Physical Slot: 1 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: 64 bytes Bus: primary=0e, secondary=0f, subordinate=0f, sec-latency=64 I/O behind bridge: 0000f000-00000fff Memory behind bridge: f1c00000-f1cfffff Prefetchable memory behind bridge: 00000000fff00000-00000000000fffff Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Bridge: PM- B3+ Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [80] Subsystem: Device 5678:1234 Capabilities: [90] Express (v1) PCI/PCI-X Bridge, MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ BrConfRtry- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- 0f:00.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller Subsystem: Texas Instruments Device ac48 Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 255 Region 0: Memory at f1c00000 (32-bit, non-prefetchable) [disabled] [size=4K] Bus: primary=00, secondary=00, subordinate=00, sec-latency=0 Memory window 0: 00000000-00000000 [disabled] (prefetchable) Memory window 1: 00000000-00000000 [disabled] (prefetchable) I/O window 0: 00000000-00000003 [disabled] I/O window 1: 00000000-00000003 [disabled] BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt- PostWrite- 16-bit legacy interface ports at 0001 dmesg with 'pci=assign-busses': ------------------------------- pci 0000:05:00.0: supports D1 D2 decode_hpp: Could not get hotplug parameters. Use defaults lspci -vvv with 'pci=assign-busses': ------------------------------------ 05:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03) (prog-if 00 [Normal decode]) Physical Slot: 1 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- Bus: primary=00, secondary=00, subordinate=00, sec-latency=64 I/O behind bridge: 00000000-00000fff Memory behind bridge: 00000000-000fffff Prefetchable memory behind bridge: 0000000000000000-00000000000fffff Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- <SERR- <PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Bridge: PM- B3+ Capabilities: [60] MSI: Enable- Count=1/16 Maskable- 64bit+ Address: 0000000000000000 Data: 0000 Capabilities: [80] Subsystem: Device 5678:1234 Capabilities: [90] Express (v1) PCI/PCI-X Bridge, MSI 00 DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <64ns, L1 <1us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+ BrConfRtry- MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr- AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Greetings, Stefani ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2009-10-26 7:28 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2009-09-29 18:23 PCI Express-to-PCI Bridge: yenta_cardbus no bus associated! Stefani Seibold 2009-09-29 23:15 ` Rafael J. Wysocki 2009-10-24 14:03 ` Stefani Seibold 2009-10-24 20:34 ` Matthew Wilcox 2009-10-25 8:10 ` Stefani Seibold 2009-10-25 8:38 ` Dominik Brodowski 2009-10-26 7:27 ` Stefani Seibold
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox