Re: [9fans] usb ohci support arrives -- another caution

[Sape Mullender <sape@plan9.bell-labs.com>]

> If you do rebuild a kernel with the new usb interface, and you have
> a usb mouse with a scroll wheel, you must ensure that usb/usbmouse
> is started with the '-s' flag (e.g. in /bin/usbstart), or your
> mouse won't work at all.  I'll submit a patch for this shortly.

Yes, the mouse driver should get the configuration descriptor and
interpret it.  USB audio does that too, but the mouse was mostly
done as a quick hack to get it working.  It would be nice if somebody
did a proper job.

Speaking of proper jobs, we'd really approciate a volunteer or two
undertaking to work on USB keyboards and serial ports.

USB ethernet adapters may be a bit much to ask and so may bluetooth, but
hey, if somebody has the energy  ... ?


Geoff also pushed the man page usb(3); check this to see how the new
endpoint (ep) command works.  We used to distinguish only isochronous
from everything else, but in OHCI, we need to distinguish between Control,
Interrupt and Bulk too.  A mouse, in the UHCI world, was treated as a
Bulk device.  In the OHCI world it's an Interrupt device (meaning the h/w
polls it every 10 ms (and this number 10 should be gotten from the
configuration descriptor, which it isn't right now)).


	Sape