public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: test11-pre6 still very broken
Date: 18 Nov 2000 10:17:17 -0800	[thread overview]
Message-ID: <8v6h3d$rp$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0011171935560.1796-100000@saturn.homenet> <20001117223137.A26341@wirex.com> <3A162EFE.A980A941@talontech.com> <20001117235624.B26341@wirex.com>

In article <20001117235624.B26341@wirex.com>, Greg KH  <greg@wirex.com> wrote:
>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.

I'd disagree.  UHCI has tons of advantages, not the least of which is
[Cthat it was there first and is widely available.  If OHCI hadn't been
done we'd have _one_ nice good USB controller implementation instead of
fighting stupid and unnecessary battles that shouldn't have existed in
the first place. 

For example, the UHCI root hub can be controlled without DMA, which
makes it a lot cheaper on the system. When a UHCI system is unconnected
and idle, it doesn't waste cycles on extra memory traffic the way OHCI
does.

UHCI also requires fewer transistors, and is the more common by far
simply because Intel is good at getting their chipsets out.

Basically, the advantages of OHCI are not worth the differentiation, and
are not always advantages at all.  Many people think that it is "good"
that the root hub looks more like a regular hub, but that's just wrong. 

Especially with faster speeds, the memory pressure of the USB controller
is going to be noticeable, and it would be much preferable if the root
directory of the USB tree would be separated out (and cached in the
controller) by the root hub.  The UHCI approach of making the root a bit
special should be taken _further_, and not seen as a mistake. 

I hope EHCI makes it all moot. Some way or another.

			Linus
-
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/

  parent reply	other threads:[~2000-11-18 18:48 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
     [not found]           ` <8v6h3d@penguin.transmeta.com>
2000-11-18 17:00             ` Pavel Machek
2000-11-18 18:17           ` Linus Torvalds [this message]
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='8v6h3d$rp$1@penguin.transmeta.com' \
    --to=torvalds@transmeta.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