What to do with all of the USB UHCI drivers in the kernel?

[Greg KH <greg@kroah.com>]

Ok, now that 2.5.16 is out, we have a total of 4 different USB UHCI
controller drivers in the kernel!  That's about 3 too many for me :)

So what to do?  I propose the following:

  From now until July 1, I want everyone to test out both the uhci-hcd
  and usb-uhci-hcd drivers on just about every piece of hardware they
  can find.  This includes SMP, UP, preempt kernels, big and little
  endian machines, and loads of different types of USB devices.

  (Note, for those who don't realize it, the uhci-hcd driver is based
  off of the uhci.c driver, and the usb-uhci-hcd driver is based off of
  the usb-uhci.c driver.  Both of these drivers now use the USB HCD
  interface, hopefully reducing some code complexity and size because of
  this.  So this means that the uhci.c and usb-uhci.c drivers are
  going to go away, just like the usb-ohci.c driver did in 2.5.16.)

  Let me (and the linux-usb-devel list) know about any thoughts you have
  pertaining to liking one of the drivers over the other one.  Speed
  tests, size tests, code pretty tests, comment spelling tests,
  documentation tests, you name it, I want to know about it.  If you
  don't want your comments to be public, send them to me directly and I
  will not let anyone else know what you said, but will use the info to
  try to pick which one should stay.

  I will be doing the same thing (running speed tests, and hardware
  tests) and will be publishing those results on the linux-usb-devel
  list for others to verify.

  Then, the week of July 1, I will be taking everyone's comments and
  making a decision about which driver to keep.

thanks,

greg k-h