Tag 'xf86-input-joystick-1.2.1' created by Sascha Hlusiak <[EMAIL PROTECTED]> 
at 2007-04-21 01:10 +0000

Joystick Driver Version 1.2.1

Changes since xf86-input-joystick-1.2.0:
Sascha Hlusiak (18):
      jstkVersionRec: Use macros for module version. Fixes #10498
      Check for Joystick API Version >=1 instead of >=2
      Don't return NULL on jstCorePreInit fail, fixes X crash.
      Fixed remaining opened filedescriptors, if ioctl fails
      Fixed DEVICE_ON still returning Success on error opening device, 
resulting in a crash
      Fixed wrong type in ioctl call for detecting buttons and axes
      Typo in linux_jstk.c: Info about number of axes and buttons was 
interchanged
      Fixed correct calculation of absolute axis position when centered
      Added extra device dependend data for different platforms.
      Added USB-HID backend for *BSD
      Replaced xf86CheckXXXOption with xf86SetXXXOption, Fixed possible NULL 
pointer dereference
      Wrapped enums and structs in typedefs
      Cosmetic changes to structs, got rid of XFree86LOADER blocks
      Got rid of JoystickDevRec->axes and JoystickDevRec->buttons, since not 
really needed.
      Fixed possible double close of device in case of error.
      Considering JS_EVENT_INIT events as real events again
      Fixed accelerated axis movement not working the first time after startup
      Fixed wrong button number reported by bsd_jstk.c.

---
 configure.ac       |   42 +++----
 man/joystick.man   |   13 +-
 src/Makefile.am    |   17 ++
 src/bsd_jstk.c     |  315 +++++++++++++++++++++++++++++++++++++++++++++++++++++
 src/jstk.c         |  131 ++++++++--------------
 src/jstk.h         |  130 +++++++++++----------
 src/jstk_axis.c    |   40 +++---
 src/jstk_hw.h      |   38 ++++++
 src/jstk_options.c |   29 ++--
 src/jstk_options.h |    2 
 src/linux_jstk.c   |   53 +++++---
 src/linux_jstk.h   |   33 -----
 12 files changed, 589 insertions(+), 254 deletions(-)
---


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to