On Thu, 29 Nov 2001, O. Beaudoux wrote: > Hi, > > I use a same code than evdev.c to scan more than one device states. This > code is embedded in threads, one thread by detected device. The trouble > comes from the "read" function call: it freeze the thread execution > until the associated device state has changed (and doing so, others > thread cannot run so we don't see other devices' activity). > > So my question is: is there a mean to query if a /dev/input/eventX as > something *new* to say before running the read function (sorry, this is > surely a beginner'squestion) ? I know the problem is solved using some > fork but threads are so nices...! > Did you try using select, poll or opening the device using O_NONBLOCK ?
-- Johann Deneux _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
