> My USB modules have varying semantics:
> [...]
> Mouse and keyboard device drivers have a non-zero usage count whenever
> they are plugged in. Any explicit mouse open further increments the usage
> count. Keyboards [...]
Hmm... not in my experience, as shown below, taken in a 2.3.99-pre3 host
with an usb mouse plugged in:
rudo.root# cat /proc/modules
usb-ohci 13528 0 (unused)
usbcore 45504 1 [usb-ohci]
ok.
rudo.root# modprobe usbmouse
rudo.root# cat /proc/modules
usbmouse 1336 0 (unused)
input 1936 2 [usbmouse]
usb-ohci 13528 0 (unused)
usbcore 45504 1 [usbmouse usb-ohci]
note, usbmouse unused
rudo.root# modprobe mousedev
rudo.root# cat /proc/modules
mousedev 3676 0
usbmouse 1336 0 (unused)
input 1936 2 [mousedev usbmouse]
usb-ohci 13528 0 (unused)
usbcore 45504 1 [usbmouse usb-ohci]
mousedev unused too. Use it:
rudo.root# cat /dev/usbmouse &
[1] 1944
rudo.root# cat /proc/modules
mousedev 3676 1
usbmouse 1336 0 (unused)
input 1936 2 [mousedev usbmouse]
usb-ohci 13528 0 (unused)
usbcore 45504 1 [usbmouse usb-ohci]
mousedev is used, but usbmouse is not. Yes, moving the mouse produces
data to /dev/usbmouse (and garbles the screen according to job %1.
I think your description is the one I would like to see, but the current
implementation is not like that.
Cheers
/alessandro
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
