From: Johannes Erdfelt <johannes@erdfelt.com>
To: "Maksim (Max) Krasnyanskiy" <maxk@qualcomm.com>
Cc: Greg KH <greg@kroah.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net
Subject: Re: What to do with all of the USB UHCI drivers in the kernel ?
Date: Tue, 21 May 2002 16:58:26 -0400 [thread overview]
Message-ID: <20020521165826.H2645@sventech.com> (raw)
In-Reply-To: <5.1.0.14.2.20020521122422.06b21188@mail1.qualcomm.com> <5.1.0.14.2.20020521122422.06b21188@mail1.qualcomm.com> <20020521195925.GA2623@kroah.com> <5.1.0.14.2.20020521133408.068d2ef8@mail1.qualcomm.com>
On Tue, May 21, 2002, Maksim (Max) Krasnyanskiy <maxk@qualcomm.com> wrote:
>
> > > So basically I vote for usb-uhci. However some things will have to be
> > > fixed. We (Bluetooth folks) have couple
> > > of devices that refuse to work with usb-uhci (I didn't test the latest
> > > usb-uhci though).
> >
> >Sorry for the confusion, but both usb-uhci.c and uhci.c will be deleted
> >anyway :)
> I thought that usb-uhci-hcd and uhci-hcd are direct derivatives of usb-uhci
> and uhci
> (ie just minor API changes). And therefor perform exactly the same.
I wouldn't consider it a minor API change, but theoretically they should
perform identically. Since some changes were non trivial, I wouldn't
guarantee that they behave identically :)
However, I'm not sure that's all that interesting. The code is a
straight enough port over that if there are bugs, they'll be there in
both versions, except for some trivial porting mistakes. Those are easy
to find and easy to fix normally.
The other kinds of bugs, like fundamental design flaws or bugs that
have always been there, are more interesting and likely to be in both.
IMO, I think testing with usb-uhci.c and uhci.c is still useful, but
testing with the -hcd variants is the most ideal since that will be the
final code base.
JE
next prev parent reply other threads:[~2002-05-21 20:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 19:41 What to do with all of the USB UHCI drivers in the kernel ? Maksim (Max) Krasnyanskiy
2002-05-21 19:59 ` Greg KH
2002-05-21 20:43 ` Maksim (Max) Krasnyanskiy
2002-05-21 20:58 ` Johannes Erdfelt [this message]
2002-05-22 1:04 ` Maksim (Max) Krasnyanskiy
2002-05-22 4:33 ` [linux-usb-devel] " David Brownell
2002-05-22 18:57 ` Maksim (Max) Krasnyanskiy
2002-05-22 5:06 ` Greg KH
2002-05-22 19:43 ` Maksim (Max) Krasnyanskiy
2002-05-21 20:00 ` [linux-usb-devel] " Johannes Erdfelt
2002-05-21 21:09 ` Maksim (Max) Krasnyanskiy
-- strict thread matches above, loose matches on Subject: below --
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 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=20020521165826.H2645@sventech.com \
--to=johannes@erdfelt.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=maxk@qualcomm.com \
/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