public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: gowdy@slac.stanford.edu
Cc: Greg KH <greg@kroah.com>, 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 16:25:50 +0200	[thread overview]
Message-ID: <3CECFBEE.9010802@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0205230746500.1824-100000@router-273.sgowdy.org>

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 else?

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.

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.
(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.

Thank's in advance.

BTW> one of the reasons I never bothered myself with kbuild-2.5
is for example that nio matter how frequently Keith
is advertising it - every time I go there to have a look at it
at sf what I find is a scatter heap of .tar.gz. The documentation
about how to install it makes me nervous, since I would
rather just expect a diff and a README how to use it, so I never
look after it.


  reply	other threads:[~2002-05-23 15:29 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 [this message]
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
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=3CECFBEE.9010802@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