Martin Dalecki wrote:
Uz.ytkownik Greg KH napisa?:
Anyway, here's the documentation that you need:
The module usb-ohci is now gone. Use ohci-hcd instead.
The people with UHCI controllers have a big more documentation to read:
The module uhci is now gone. If you used this module,
1. Rename usb-ohci to usb-ohci-old
Keeping the old-style drivers would defeat the purposes
of having new-style ones, though.
2. Rename ohci-hcd to usb-ohci
But during the transition period when both exist, what then?
And later when someone says I'm using the usb-ohci driver (or
since
open-host-contoller-interface-host-controller-[driver]...
Quite a lot of semanticla duplication if you ask me.
If you split all acronyms into their component atoms
before coming up with new names, I think you'll end
up changing quite a lot of technology nomenclature.
(Avoid starting names
Using that -hcd suffix is completely unambiguous.
(But if we go with the usb-uhci-hcd driver I'd vote
to rename it as uhci-hcd.)
I didn't kown ohci was already used.
But if anything I would prefer the usb- prefix over
the -hcd suffix and a move away of the old driver which
occupied
Peter Wächtler wrote:
Martin Dalecki wrote:
Uz.ytkownik Greg KH napisa?:
Anyway, here's the documentation that you need:
The module usb-ohci is now gone. Use ohci-hcd instead.
The people with UHCI controllers have a big more documentation to read:
The module uhci is now
I don't have a problem with the new names. Users shouldn't care, and when
they do they want to report problems. It would help to know what they are
actually talking about without need to remember which kernel the rename
happened in (and that distributions may backport the changes to earlier
Stephen J. Gowdy wrote:
I don't have a problem with the new names. Users shouldn't care, and when
they do they want to report problems.
You like to get these reports ?
USB does no longer works, since I upgraded to 2.5
It would help to know what they are
actually talking about without need
On Fri, 24 May 2002, Gunther Mayer wrote:
Stephen J. Gowdy wrote:
I don't have a problem with the new names. Users shouldn't care, and when
they do they want to report problems.
You like to get these reports ?
USB does no longer works, since I upgraded to 2.5
Best part of my day.
Hi Martin,
What do you actually want to know? That an EHCI controller should
use the ehci-hcd driver and that the OHCI controller should use the
ohci-hcd controller? Or that the uhci-* drivers can't drive a EHCI or OHCI
controller? Or something else?
Uz.ytkownik Stephen J. Gowdy napisa?:
Hi Martin,
What do you actually want to know? That an EHCI controller should
use the ehci-hcd driver and that the OHCI controller should use the
ohci-hcd controller? Or that the uhci-* drivers can't drive a EHCI or OHCI
controller? Or something
Martin Dalecki wrote:
Uz.ytkownik Stephen J. Gowdy napisa?:
Hi Martin,
What do you actually want to know? That an EHCI controller should
use the ehci-hcd driver and that the OHCI controller should use the
ohci-hcd controller? Or that the uhci-* drivers can't drive a EHCI or OHCI
On Thu, May 23, 2002 at 04:25:50PM +0200, Martin Dalecki wrote:
Well what I know is the following: Kudzu did set up my system
to use usb-ohci driver similar. And now you have apparently
started to obsolete some of them. I know that there are still
two drivers supported. So I would really
Uz.ytkownik Greg KH napisa?:
Anyway, here's the documentation that you need:
The module usb-ohci is now gone. Use ohci-hcd instead.
The people with UHCI controllers have a big more documentation to read:
The module uhci is now gone. If you used this module, use
13 matches
Mail list logo
