From: Martin Dalecki <dalecki@evision-ventures.com>
To: Greg KH <greg@kroah.com>
Cc: gowdy@slac.stanford.edu, Andre Bonin <kernel@bonin.ca>,
linux-usb-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Linux-usb-users@lists.sourceforge.net
Subject: Re: [Linux-usb-users] Re: What to do with all of the USB UHCI drivers in the kernel?
Date: Thu, 23 May 2002 19:55:01 +0200 [thread overview]
Message-ID: <3CED2CF5.5050202@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205230746500.1824-100000@router-273.sgowdy.org> <3CECFBEE.9010802@evision-ventures.com> <20020523160410.GC11153@kroah.com>
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
> uhci-hcd instead. The module usb-uhci is now gone. If you used
> this module, use usb-uhci-hcd instead. If you have a preference
> over which UHCI module works better for you, please email
> greg@kroah.com your comments, as one of these modules will be
> going away in the near future.
Thank's that is explaining it.
But I would have loved it if it appeared with + in front in
the patch somewhere. That's the only true problem I had.
OK?
BTW.> usb-ohci seems to be a more reasonable name, since
it tells me directly - hey buddy I'm USB the -hcd doen't
tell me anything in addition and is entierly redundant, or
is there a ohci.o module there?
And why not just doing the following.
1. Rename usb-ohci to usb-ohci-old
2. Rename ohci-hcd to usb-ohci
Much less grief and guessing what happens :-).
Just a suggestion.
next prev parent reply other threads:[~2002-05-23 18:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-20 22:31 What to do with all of the USB UHCI drivers in the kernel? Greg KH
2002-05-21 15:23 ` [Linux-usb-users] " Timothy E. Jedlicka - wrk
2002-05-21 20:10 ` Greg KH
2002-05-22 1:10 ` André Bonin
2002-05-22 19:21 ` Greg KH
2002-05-22 19:35 ` Andre Bonin
2002-05-22 20:15 ` Greg KH
2002-05-23 6:34 ` Martin Dalecki
2002-05-23 14:48 ` [Linux-usb-users] " Stephen J. Gowdy
2002-05-23 14:25 ` Martin Dalecki
2002-05-23 15:11 ` [Linux-usb-users] Re: What to do with all of the USB UHCI driversin " Gunther Mayer
2002-05-23 15:42 ` kb25 manual [was Re: [Linux-usb-users] Re: What to do with all of the USB UHCI drivers in the kernel?] Tomas Szepe
2002-05-23 15:51 ` Randy.Dunlap
2002-05-23 16:01 ` Tomas Szepe
2002-05-23 17:46 ` Martin Dalecki
2002-05-23 19:09 ` Tomas Szepe
2002-05-23 16:04 ` [Linux-usb-users] Re: What to do with all of the USB UHCI drivers in the kernel? Greg KH
2002-05-23 17:55 ` Martin Dalecki [this message]
2002-05-24 8:21 ` [Linux-usb-users] Re: What to do with all of the USB UHCI drivers Peter Wächtler
2002-05-24 14:07 ` Gunther Mayer
2002-05-24 15:13 ` Stephen J. Gowdy
2002-05-23 15:16 ` [linux-usb-devel] Re: What to do with all of the USB UHCI drivers in the kernel? David Brownell
2002-05-23 17:41 ` Peter Osterlund
2002-05-23 17:48 ` Greg KH
2002-05-23 18:16 ` Peter Osterlund
2002-05-23 19:24 ` Pierre Rousselet
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=3CED2CF5.5050202@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=Linux-usb-users@lists.sourceforge.net \
--cc=gowdy@slac.stanford.edu \
--cc=greg@kroah.com \
--cc=kernel@bonin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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