From: Greg KH <greg@wirex.com>
To: Ben Ford <bford@talontech.com>
Cc: David Ford <david@linux.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: test11-pre6 still very broken
Date: Fri, 17 Nov 2000 23:56:24 -0800 [thread overview]
Message-ID: <20001117235624.B26341@wirex.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011171935560.1796-100000@saturn.homenet> <8v4306$sga$1@cesium.transmeta.com> <3A161337.6A1BE826@linux.com> <20001117223137.A26341@wirex.com> <3A162EFE.A980A941@talontech.com>
In-Reply-To: <3A162EFE.A980A941@talontech.com>; from bford@talontech.com on Fri, Nov 17, 2000 at 11:25:50PM -0800
On Fri, Nov 17, 2000 at 11:25:50PM -0800, Ben Ford wrote:
> Here is lspci output from the laptop in question. Is this not UHCI?
Yes it is. Just a bit funny if you think about it, but with Intel and
Via putting the UHCI core into their chipsets I guess it makes sense.
One note for the archives, if you are presented a choice between a OHCI
or a UHCI controller, go for the OHCI. It has a "cleaner" interface,
handles more of the logic in the silicon, and due to this provides
faster transfers.
In it's defense, the UHCI design was the first one, and OHCI
capitalized on that by fixing some of its weaknesses. Hopefully the
same thing will not happen for USB 2.0, and everyone will like EHCI.
greg k-h
(who has UHCI in all of his machines except one.)
--
greg@(kroah|wirex).com
http://immunix.org/~greg
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-18 8:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-17 20:00 test11-pre6 still very broken Tigran Aivazian
2000-11-17 20:04 ` H. Peter Anvin
2000-11-18 5:27 ` David Ford
2000-11-18 6:31 ` Greg KH
2000-11-18 7:14 ` Jeff Garzik
2000-11-18 7:25 ` Ben Ford
2000-11-18 7:56 ` Greg KH [this message]
[not found] ` <8v6h3d@penguin.transmeta.com>
2000-11-18 17:00 ` Pavel Machek
2000-11-18 18:17 ` Linus Torvalds
2000-11-20 12:37 ` Thomas Sailer
2000-11-20 12:47 ` Vojtech Pavlik
2000-11-21 11:35 ` Thomas Sailer
2000-11-18 0:29 ` Keith Owens
2000-11-18 4:38 ` Keith Owens
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=20001117235624.B26341@wirex.com \
--to=greg@wirex.com \
--cc=bford@talontech.com \
--cc=david@linux.com \
--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