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/