From: Vojtech P. <vo...@su...> - 2001-08-02 18:31:01
|
On Thu, Aug 02, 2001 at 11:13:21AM -0700, Charles Duffy wrote: > Being able to wake the mouse driver from more than one source (ie. > separately for /proc/input/devices and /dev/input/eventX) will require > a level of app restructuring in more than one case which I believe is > unnecessary and will reduce driver availability without good cause. Would there be a problem with 1) Opening and parsing /proc/input/devices. 1a) If no device is found either go to 1) if non-blocking is required or select() on /proc/input/devices and then go to 1) 2) Opening the correct /proc/input/eventX 3) Read the event data 4) If -ENODEV received go to 1) We can't sanely mix all event sources into one, because there are devices which generate lots of events and it'd be not a good idea in my opinion to feed all of them to the app. -- Vojtech Pavlik SuSE Labs |