From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: USB ohci vs ehci
Date: Mon, 27 Jun 2005 18:03:13 -0600 [thread overview]
Message-ID: <42C093C1.9090008@shaw.ca> (raw)
In-Reply-To: <4k9XR-2VC-35@gated-at.bofh.it>
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/
next parent reply other threads:[~2005-06-28 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4k9XR-2VC-37@gated-at.bofh.it>
[not found] ` <4k9XR-2VC-35@gated-at.bofh.it>
2005-06-28 0:03 ` Robert Hancock [this message]
[not found] <4789af9e05062714493e18fe0b@mail.gmail.com>
2005-06-27 22:03 ` 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=42C093C1.9090008@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@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