2) There is not 'interrupt' facility./ The host machine (OK, the USB
inteface chip) has to keep on poollign the keyboard to
see if a key has
changed state, and keep on pollign the mouse to see if it has moved. That
seesm to be totally the wrong thing to do.. Heck, even the HP9830 has an
intettupt on keypress.
-tony
Actually, the HID (human interface device) class used by mice and keyboards does use an
interrupt.? Also, on the device side, pretty much all the transfers can generate an
interrupt, depending on how you configure the register.? Also, it's possible to just
bypass all the pre-canned "device classes" and just drive the USB raw, which
works just fine, and on many small processors is not much more work than driving the
UART.? In fact, for some transmissions, it's simpler because you can get just one
interrupt for a whole transmission, rather than buffering and error-checking a
transmission one byte at at time.
I'm not arguing that USB is as easy as a regular UART interface--it's not by a
long shot.
Dave