From: Jim Ramsay <jim.ramsay@gmail.com>
To: linux-ide@vger.kernel.org
Subject: USB ohci vs ehci
Date: Mon, 27 Jun 2005 15:49:55 -0600 [thread overview]
Message-ID: <4789af9e05062714493e18fe0b@mail.gmail.com> (raw)
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!"
next reply other threads:[~2005-06-27 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 21:49 Jim Ramsay [this message]
2005-06-27 22:04 ` USB ohci vs ehci Jim Ramsay
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=4789af9e05062714493e18fe0b@mail.gmail.com \
--to=jim.ramsay@gmail.com \
--cc=linux-ide@vger.kernel.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).