public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gunther Mayer <gunther.mayer@gmx.net>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: Greg KH <greg@kroah.com>,
	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 driversin  the kernel?
Date: Thu, 23 May 2002 17:11:06 +0200	[thread overview]
Message-ID: <3CED068A.870BC1D8@gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0205230746500.1824-100000@router-273.sgowdy.org> <3CECFBEE.9010802@evision-ventures.com>

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
> > controller? Or something else?
>

Rename the old driver to *-old.
Rename the new drivers to the "normal" names.

There is no reason to confurce the userbase to fiddle
with their configurations. You said the old drivers could
seamlessly be replacedby s.th. better, so this policy will
implement this at it's best.

You will immediately get a lot of testing !!!

Regards, Gunther





  reply	other threads:[~2002-05-23 16:11 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               ` Gunther Mayer [this message]
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=3CED068A.870BC1D8@gmx.net \
    --to=gunther.mayer@gmx.net \
    --cc=Linux-usb-users@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --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