From: Greg KH <greg@kroah.com>
To: Martin Dalecki <dalecki@evision-ventures.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 09:04:10 -0700 [thread overview]
Message-ID: <20020523160410.GC11153@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205230746500.1824-100000@router-273.sgowdy.org> <3CECFBEE.9010802@evision-ventures.com>
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 really wellcome it
> if you would just write up some documentation about the *whole*
> transition from using some old driver to the one which is
> supposed to be the driver used in the future.
Hm, Kudzu shouldn't care, you just should not be able to load the
usb-ohci module on startup. At least that's what happens to me on my
boxes.
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.
> Most likely this would be of course module aliasing entires
> which could be used in /etc/modules.conf to cheat around
> kudzu - this way it would be for example possible
> to have a nice dual boot configuration.
Heh, I don't mess around with module aliasing, so I don't know the first
thing of what to do in this situation. Someone reading the above
documentation should be able to figure it all out.
> (I can adjust my boot scripts to set up an apriopriate symlink
> from /etc/modules.conf to modules-2.5.18.confg and
> modules-2.4.18.conf debpending what I'm booting anyway...)
>
> In short - if you change something about the configuration
> and usage - just document it please.
We really don't use CHANGES anymore. Where do you propose things like
the above few sentences go to where everyone will know to look?
thanks,
greg k-h
next prev parent reply other threads:[~2002-05-23 16:04 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 ` Greg KH [this message]
2002-05-23 17:55 ` [Linux-usb-users] Re: What to do with all of the USB UHCI drivers in the kernel? Martin Dalecki
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=20020523160410.GC11153@kroah.com \
--to=greg@kroah.com \
--cc=Linux-usb-users@lists.sourceforge.net \
--cc=dalecki@evision-ventures.com \
--cc=gowdy@slac.stanford.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.