Lines Matching +full:wait +full:- +full:queue

1 .. _joystick-api:
7 :Author: Ragnar Hojland Espinosa <ragnar@macula.net> - 7 Aug 1998
18 driver now reports only any changes of its state. See joystick-api.txt,
65 -------------
86 ---------------
108 --------------
110 For an axis, ``value`` is a signed integer between -32767 and +32767
141 -------------
153 wait) forever until an event is generated and effectively read. There
154 are two alternatives if you can't afford to wait forever (which is,
157 	a) use select to wait until there's data to be read on fd, or
161 	b) open the device in non-blocking mode (O_NONBLOCK)
165 ----------
167 If read returns -1 when reading in O_NONBLOCK mode, this isn't
169 are no events pending to be read on the driver queue. You should read
170 all events on the queue (that is, until you get a -1).
180 		/* EAGAIN is returned when the queue is empty */
187 One reason for emptying the queue is that if it gets full you'll start
188 missing events since the queue is finite, and older events will get
194 Why can the queue get full? Because you don't empty the queue as
196 and too many events to store in the queue get generated. Note that
199 If time between reads is enough to fill the queue and lose an event,
207  As of version 1.2.8, the queue is circular and able to hold 64
219 In this case, read would return -1 if the queue was empty, or some
222 process the events and keep reading it until you empty the driver queue.
245 -------------
247 JSIOGCVERSION is a good way to check in run-time whether the running
249 IOCTL will fail. For a compile-time decision, you can test the
257 ----------
259 JSIOCGNAME(len) allows you to get the name string of the joystick - the same
271 -------------
331 except that the values are non-negative. The 1.2.8+ drivers use a