> fwiw, i recompiled with the je uhci driver and it seems to be working.
> if anyone has patch suggestions for the normal uhci driver,
> i'll be glad to try them though.
>
> btw, what are the differences between the two? are they both being
> actively developed? is one more efficient than the other? is one the
> future?
Here's what Johannes Erdfelt wrote about this Sunday night:
<quote>
Just as a quick note to clarify, the uhci.c and usb-uhci.c drivers are
fundamentally different in many areas.
Some of the code is similar (from a previous common version of the code)
but that is only some really basic code to start/stop the HC and
initialization of the controller. Even this is starting to deviate some
bit.
This is why there are 2 different drivers for the same device in the
kernel, because they are so different.
However, a patch has been posted to the linux-usb lists (follow the link
archives on http://www.linux-usb.org) for usb-uhci.c to fix the slab
poisoning related bugs.
JE
</quote>
I'll add this.
The fix-slab-poisoning patches for usb-uhci were posted to the
linux-usb mailing list Saturday (2 patch files) and were sent
to Linus yesterday.
The goal is to have only one uhci host controller driver.
They are both still being actively developed/supported.
They are basically in a "duel" with each other to see which
one stays in the kernel. That is the only POV in which one
of them is the "future."
Unfortunately we have reports that some devices work with
only one of the uhci drivers [or the other driver for some
other devices].
~Randy
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon May 15 2000 - 21:00:25 EST