linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: "Timothy A. Seufert" <tas@mindspring.com>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: usb wheel mouse, XF4.0
Date: Wed, 29 Nov 2000 14:10:42 +0100	[thread overview]
Message-ID: <19341024064226.19088@192.168.1.2> (raw)
In-Reply-To: <v04220801b64a66c6a467@[10.0.0.42]>


>
>The OHCI driver should support literally any standards compliant OHCI
>USB controller found on PCI, whether it's integrated into a
>multifunction IO chip or on a card.  If it doesn't work, there's a
>bug somewhere, either in the hardware (in which case it probably
>doesn't comply to the standard) or in the driver (most likely
>initialization related).

There are various HW bugs in the first revisions of OHCI controllers that
appeared (and so the first USB PCI cards for macs). Looking at Apple driver,
they have a list of vendorIDs/deviceIDs/rev with, for each one, a bitmask of
known "workarounds" to apply depending on the controller. We don't have
such thing in Linux.

>The same principle applies to UHCI.  UHCI could work on PPC, but
>nobody has ever bothered, because the installed base of UHCI
>controllers on PPC boxes approximates zero.  Apple's built-in USB is
>always OHCI, and their MacOS drivers only support OHCI, so anybody
>who wants to market a PCI USB card for Macs uses a OHCI chip to take
>advantage of the drivers written by Apple.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-11-29 13:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10011282036580.22745-100000@opal.biophys.uni-duesseldorf.de >
2000-11-29  8:15 ` usb wheel mouse, XF4.0 Timothy A. Seufert
2000-11-29  9:30   ` Michael Schmitz
2000-11-29 13:10   ` Benjamin Herrenschmidt [this message]
     [not found] <Pine.LNX.4.10.10011282109440.2086-100000@zirkon.biophys.uni-duessel dorf.de>
2000-11-28 22:32 ` Stefan Jeglinski
2000-11-28 23:15   ` Michael Schmitz
     [not found] <Pine.LNX.4.10.10011282036580.22745-100000@opal.biophys.uni-duesseld orf.de>
2000-11-28 19:55 ` Stefan Jeglinski
2000-11-28 20:23   ` Michael Schmitz
2000-11-29  8:33   ` Timothy A. Seufert
2000-11-29  9:02     ` Andreas Tobler
2000-11-29 14:07       ` Stefan Jeglinski
2000-11-29 17:08         ` Benjamin Herrenschmidt
2000-11-29 17:14         ` Benjamin Herrenschmidt
2000-12-01  7:09           ` Michel Lanners
2000-11-29 13:45     ` christopher.murtagh
     [not found] <F269nW0kKIBXEHt3V5g00007774@hotmail.com>
2000-11-28 19:31 ` Stefan Jeglinski
2000-11-28 19:39   ` Michael Schmitz

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=19341024064226.19088@192.168.1.2 \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=tas@mindspring.com \
    /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).