Searched hist:240891 (Results 1 - 2 of 2) sorted by relevance
/freebsd-10.1-release/etc/ | ||
H A D | devd.conf | diff 240891 Mon Sep 24 15:27:42 MDT 2012 hselasky Make sure moused is exiting as quick as possible after that the umsX character device returns a read error. Update devd.conf rules to use "DEVFS" events which are generated after that the umsX character device node has been created/destroyed, and then there should be no need for moused to wait up to 10 seconds for umsX to be ready. Opening umsX should not fail except if the kernel is low on memory. In that case the user can replug the USB mouse or use "usbconfig" to reset the device. In case of USB mouse devices, moused should neither retry to open its character device, once the first read error has happened. This is an indication of device detach. MFC after: 1 week |
/freebsd-10.1-release/usr.sbin/moused/ | ||
H A D | moused.c | diff 240891 Mon Sep 24 15:27:42 MDT 2012 hselasky Make sure moused is exiting as quick as possible after that the umsX character device returns a read error. Update devd.conf rules to use "DEVFS" events which are generated after that the umsX character device node has been created/destroyed, and then there should be no need for moused to wait up to 10 seconds for umsX to be ready. Opening umsX should not fail except if the kernel is low on memory. In that case the user can replug the USB mouse or use "usbconfig" to reset the device. In case of USB mouse devices, moused should neither retry to open its character device, once the first read error has happened. This is an indication of device detach. MFC after: 1 week |
Completed in 65 milliseconds