* USB ohci vs ehci
@ 2005-06-27 21:49 Jim Ramsay
2005-06-27 22:03 ` Jim Ramsay
2005-06-27 22:04 ` Jim Ramsay
0 siblings, 2 replies; 4+ messages in thread
From: Jim Ramsay @ 2005-06-27 21:49 UTC (permalink / raw)
To: linux-ide
I have an NEC-based 'UP215-N101' USB 2.0 PCI card which can apparently
appear as a device under ohci-hcd or ehci-hcd, depending on which one
is loaded. If both modules are loaded, the device doesn't seem to
work, as it is detected by both
I would just load the ehci-hcd device, except that the on-board USB is
only detected by ohci-hcd.
Is there some way to make ohci-hcd ignore a specific PCI device or
devices? Or is there a way ehci-hcd can tell ohci-hcd to 'forget'
about a particular device if it exists in ehci-hcd as well?
Output of `dmesg` after loading ohci-hcd. The card in question is at
pci 0000:00:10
ohci_hcd 0000:00:01.3: PCI device 1283:1234 (Integrated Technology Express, Inc.
)
ohci_hcd 0000:00:01.3: irq 35, pci mem 0xd020000
ohci_hcd 0000:00:01.3: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ohci_hcd 0000:00:10.0: NEC Corporation USB
ohci_hcd 0000:00:10.0: irq 40, pci mem 0xd021000
ohci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ohci_hcd 0000:00:10.1: NEC Corporation USB (#2)
ohci_hcd 0000:00:10.1: irq 40, pci mem 0xd022000
ohci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
Output of `dmesg` after loading ehci-hcd:
ehci_hcd 0000:00:10.2: NEC Corporation USB 2.0
ehci_hcd 0000:00:10.2: irq 40, pci mem 0xd024000
ehci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:10.2: park 0
ehci_hcd 0000:00:10.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 5 ports detected
Output of `lspci -vv -s 10`:
00:10.0 Class 0c03: 1033:0035 (rev 43) (prog-if 10)
Subsystem: 3083:0035
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Step
ping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
Latency: 252 (250ns min, 10500ns max), cache line size 08
Interrupt: pin A routed to IRQ 40
Region 0: Memory at 0d021000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.1 Class 0c03: 1033:0035 (rev 43) (prog-if 10)
Subsystem: 3083:0035
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Step
ping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
Latency: 252 (250ns min, 10500ns max), cache line size 08
Interrupt: pin B routed to IRQ 40
Region 0: Memory at 0d022000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.2 Class 0c03: 1033:00e0 (rev 04) (prog-if 20)
Subsystem: 3083:00e0
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Step
ping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
Latency: 252 (4000ns min, 8500ns max), cache line size 08
Interrupt: pin C routed to IRQ 40
Region 0: Memory at 0d024000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
--
Jim Ramsay
"Me fail English? That's unpossible!"
^ permalink raw reply [flat|nested] 4+ messages in thread
* USB ohci vs ehci
2005-06-27 21:49 Jim Ramsay
@ 2005-06-27 22:03 ` Jim Ramsay
2005-06-27 22:04 ` Jim Ramsay
1 sibling, 0 replies; 4+ messages in thread
From: Jim Ramsay @ 2005-06-27 22:03 UTC (permalink / raw)
To: Linux Kernel
I have an NEC-based 'UP215-N101' USB 2.0 PCI card which can apparently
appear as a device under ohci-hcd or ehci-hcd, depending on which one
is loaded. If both modules are loaded, the device doesn't seem to
work, as it is detected by both
I would just load the ehci-hcd device, except that the on-board USB is
only detected by ohci-hcd.
Is there some way to make ohci-hcd ignore a specific PCI device or
devices? Or is there a way ehci-hcd can tell ohci-hcd to 'forget'
about a particular device if it exists in ehci-hcd as well?
Output of `dmesg` after loading ohci-hcd. The card in question is at
pci 0000:00:10
ohci_hcd 0000:00:01.3: PCI device 1283:1234 (Integrated Technology Express, Inc.
)
ohci_hcd 0000:00:01.3: irq 35, pci mem 0xd020000
ohci_hcd 0000:00:01.3: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ohci_hcd 0000:00:10.0: NEC Corporation USB
ohci_hcd 0000:00:10.0: irq 40, pci mem 0xd021000
ohci_hcd 0000:00:10.0: new USB bus registered, assigned bus number 2
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ohci_hcd 0000:00:10.1: NEC Corporation USB (#2)
ohci_hcd 0000:00:10.1: irq 40, pci mem 0xd022000
ohci_hcd 0000:00:10.1: new USB bus registered, assigned bus number 3
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
Output of `dmesg` after loading ehci-hcd:
ehci_hcd 0000:00:10.2: NEC Corporation USB 2.0
ehci_hcd 0000:00:10.2: irq 40, pci mem 0xd024000
ehci_hcd 0000:00:10.2: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:10.2: park 0
ehci_hcd 0000:00:10.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 5 ports detected
Output of `lspci -vv -s 10`:
00:10.0 Class 0c03: 1033:0035 (rev 43) (prog-if 10)
Subsystem: 3083:0035
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Step
ping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
Latency: 252 (250ns min, 10500ns max), cache line size 08
Interrupt: pin A routed to IRQ 40
Region 0: Memory at 0d021000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.1 Class 0c03: 1033:0035 (rev 43) (prog-if 10)
Subsystem: 3083:0035
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Step
ping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
Latency: 252 (250ns min, 10500ns max), cache line size 08
Interrupt: pin B routed to IRQ 40
Region 0: Memory at 0d022000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:10.2 Class 0c03: 1033:00e0 (rev 04) (prog-if 20)
Subsystem: 3083:00e0
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Step
ping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
Latency: 252 (4000ns min, 8500ns max), cache line size 08
Interrupt: pin C routed to IRQ 40
Region 0: Memory at 0d024000 (32-bit, non-prefetchable) [size=256]
Capabilities: [40] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot
+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
--
Jim Ramsay
"Me fail English? That's unpossible!"
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: USB ohci vs ehci
2005-06-27 21:49 Jim Ramsay
2005-06-27 22:03 ` Jim Ramsay
@ 2005-06-27 22:04 ` Jim Ramsay
1 sibling, 0 replies; 4+ messages in thread
From: Jim Ramsay @ 2005-06-27 22:04 UTC (permalink / raw)
To: linux-ide
My apologies. I've sent this off to linux-kernel list instead.
Please disregard.
--
Jim Ramsay
"Me fail English? That's unpossible!"
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: USB ohci vs ehci
[not found] ` <4k9XR-2VC-35@gated-at.bofh.it>
@ 2005-06-28 0:03 ` Robert Hancock
0 siblings, 0 replies; 4+ messages in thread
From: Robert Hancock @ 2005-06-28 0:03 UTC (permalink / raw)
To: linux-kernel
Jim Ramsay wrote:
> I have an NEC-based 'UP215-N101' USB 2.0 PCI card which can apparently
> appear as a device under ohci-hcd or ehci-hcd, depending on which one
> is loaded. If both modules are loaded, the device doesn't seem to
> work, as it is detected by both
USB 2.0 controllers are supposed to be detected by both EHCI and either
OHCI or UHCI, since they support both interfaces. EHCI is only used for
USB 2.0 high-speed devices and OHCI or UHCI is used for other devices.
If the controller's not working, the problem will be something else..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-06-28 0:05 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <4k9XR-2VC-37@gated-at.bofh.it>
[not found] ` <4k9XR-2VC-35@gated-at.bofh.it>
2005-06-28 0:03 ` USB ohci vs ehci Robert Hancock
2005-06-27 21:49 Jim Ramsay
2005-06-27 22:03 ` Jim Ramsay
2005-06-27 22:04 ` Jim Ramsay
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.