[SCM] xboxdrv packaging branch, master, updated. debian/0.8.2-1-30-g7d4df49

Fri Feb 3 16:26:15 UTC 2012

The following commit has been merged in the master branch:
commit 66ed88942bbdf220e33ff537a8e17b503bdbe891
Author: Andrey Rahmatullin <wrar at wrar.name>
Date:   Fri Feb 3 22:01:05 2012 +0600

    Update debian/patches/fix-xboxdrv-manpage.patch for 0.8.4.

diff --git a/debian/patches/fix-xboxdrv-manpage.patch b/debian/patches/fix-xboxdrv-manpage.patch
index 0ebf7d7..0be9f66 100644
--- a/debian/patches/fix-xboxdrv-manpage.patch
+++ b/debian/patches/fix-xboxdrv-manpage.patch
@@ -2,10 +2,10 @@ Description: Fix xboxdrv.1 errors reported by lintian
  Fix all hyphen-used-as-minus-sign and spelling-error-in-manpage reports.
 Author: Andrey Rahmatullin <wrar at wrar.name>
 Forwarded: no
-Last-Update: 2011-08-06
+Last-Update: 2012-02-03
 
 diff --git a/doc/xboxdrv.1 b/doc/xboxdrv.1
-index 15a97d4..6aa678b 100644
+index d801ea7..b3b7bd3 100644
 --- a/doc/xboxdrv.1
 +++ b/doc/xboxdrv.1
 @@ -56,7 +56,7 @@ for more information.
@@ -28,7 +28,7 @@ index 15a97d4..6aa678b 100644
  section for better readability.
  
  The \*(T<\fIexamples/\fR\*(T> directory contains
-@@ -334,7 +334,7 @@ xpad module loaded and want to use xboxdrv without
+@@ -347,7 +347,7 @@ xpad module loaded and want to use xboxdrv without
  unloading it.
  .TP 
  \*(T<\fB\-\-generic\-usb\-spec\fR\*(T> \fINAME=VALUE,...\fR
@@ -37,7 +37,7 @@ index 15a97d4..6aa678b 100644
  endpoint \*(T<\fBgeneric\-usb\fR\*(T> will read. The
  spec as the form
  of \fINAME=VALUE,...\fR. Allowed values are:
-@@ -767,7 +767,7 @@ T}
+@@ -789,7 +789,7 @@ T}
  T{
  lt(7), rt(8)
  T}	T{
@@ -46,7 +46,7 @@ index 15a97d4..6aa678b 100644
  T}
  T{
  tl, tr
-@@ -777,7 +777,7 @@ T}
+@@ -799,7 +799,7 @@ T}
  T{
  du(up), dd(down), dl(left), dr(right)
  T}	T{
@@ -55,7 +55,7 @@ index 15a97d4..6aa678b 100644
  T}
  T{
  green, red, yellow, blue, orange
-@@ -789,7 +789,7 @@ T}
+@@ -811,7 +811,7 @@ T}
  Just like with \*(T<\fB\-\-ui\-buttonmap\fR\*(T> you can add button filter to each button.
  .TP 
  \*(T<\fB\-\-axismap\fR\*(T> \fIAXIS=MAPPING,...\fR
@@ -64,7 +64,7 @@ index 15a97d4..6aa678b 100644
  mapping. In addition you can supply a sign to indicate that an axis
  should be inverted. So if you want to invert the y1 axis start with:
  
-@@ -832,7 +832,7 @@ as autofire while another one, emitting the same signal, acts normally.
+@@ -854,7 +854,7 @@ as autofire while another one, emitting the same signal, acts normally.
  .fi
  .TP 
  \*(T<\fB\-\-axis\-sensitivty \fR\*(T>\fIAXIS=SENSITIVITY\fR,...
@@ -73,7 +73,7 @@ index 15a97d4..6aa678b 100644
  
  .nf
  \*(T<$ xboxdrv \-\-axis\-sensitivty X1=\-1.0,Y1=\-1.0\*(T>
-@@ -841,7 +841,7 @@ The sensitive of an axis can be adjusted via --axis-sensitivty:
+@@ -863,7 +863,7 @@ The sensitive of an axis can be adjusted via --axis-sensitivty:
  A value of 0 gives you the default linear sensitivity,
  values larger then 0 will give you higher sensitivity,
  while values smaller then 0 will give you lower
@@ -82,7 +82,7 @@ index 15a97d4..6aa678b 100644
  will generally give good results, everything beyond that
  won't be of much practical use.
  
-@@ -924,7 +924,7 @@ Will give you controls that are relative to your
+@@ -946,7 +946,7 @@ Will give you controls that are relative to your
  character instead of your viewpoint.
  .TP 
  \*(T<\fB\-\-four\-way\-restrictor\fR\*(T>
@@ -91,7 +91,7 @@ index 15a97d4..6aa678b 100644
  limit the movement on both analogsticks to only four
  directions (up, down, left, right), the diagonals (up/left,
  up/right, down/left, down/right) are filtered out from the
-@@ -1060,7 +1060,7 @@ switch this behaviour off.
+@@ -1082,7 +1082,7 @@ switch this behaviour off.
  \*(T<\fB\-\-device\-name NAME\fR\*(T>
  Changes the descriptive name the device will have. This
  options acts the same as
@@ -100,7 +100,7 @@ index 15a97d4..6aa678b 100644
  .TP 
  \*(T<\fB\-\-device\-names TYPE.SLOT=NAME,...\fR\*(T>
  Changes the descriptive name the device will
-@@ -1075,7 +1075,7 @@ matches everything.
+@@ -1097,7 +1097,7 @@ matches everything.
  Changes the vendor, product, version and bus id that the
  device will have. The last two arguments are optional.
  This options acts the same as
@@ -109,7 +109,7 @@ index 15a97d4..6aa678b 100644
  .TP 
  \*(T<\fB\-\-device\-usbids TYPE.SLOT=VENDOR:PRODUCT:VERSION:BUS,...\fR\*(T>
  Changes the vendor, product, version and bus id the device will
-@@ -1270,7 +1270,7 @@ is \fIVALUE\fR * axis_state.
+@@ -1292,7 +1292,7 @@ is \fIVALUE\fR * axis_state.
  gives the number of milisecond to pass before the event
  is fired again (default: 5).
  
@@ -118,7 +118,7 @@ index 15a97d4..6aa678b 100644
  the REL event being fired as soon as possible (i.e.
  every \fItimeout\fR miliseconds).
  This is the recomment way for handling mouse emulation,
-@@ -1323,7 +1323,7 @@ handler, while \*(T<\fBKEY_A\fR\*(T> is an argument for the
+@@ -1345,7 +1345,7 @@ handler, while \*(T<\fBKEY_A\fR\*(T> is an argument for the
  event handler. What kind of arguments an event handler allows
  depends on the event handler.
  .PP
@@ -127,8 +127,8 @@ index 15a97d4..6aa678b 100644
  just writing:
  .PP
  .nf
-@@ -1427,7 +1427,7 @@ will default to 'backward'.
- See \*(T<\fBcycle\-key\-named\fR\*(T> for a full example.
+@@ -1465,7 +1465,7 @@ To move backwards through the sequence another key must
+ be bound to \*(T<\fBsequence\-key\-ref\fR\*(T>.
  .TP 
  \*(T<\fBexec\fR\*(T>
 -The exec button handler allows to launch an application
@@ -136,7 +136,7 @@ index 15a97d4..6aa678b 100644
  when the button was pressed. An example would look like
  this:
  
-@@ -1506,7 +1506,7 @@ is \fIVALUE\fR * axis_state.
+@@ -1544,7 +1544,7 @@ is \fIVALUE\fR * axis_state.
  gives the number of milisecond to pass before the event
  is fired again (default: 5).
  
@@ -145,7 +145,7 @@ index 15a97d4..6aa678b 100644
  the REL event being fired as soon as possible (i.e.
  every \fItimeout\fR miliseconds).
  This is the recomment way for handling mouse emulation,
-@@ -1561,7 +1561,7 @@ when it is not pressed and in unpressed state when it is
+@@ -1599,7 +1599,7 @@ when it is not pressed and in unpressed state when it is
  pressed.
  .TP 
  \*(T<\fBauto\fR\*(T>, \*(T<\fBautofire\fR\*(T>:\fIRATE\fR:\fIDELAY\fR
@@ -154,7 +154,7 @@ index 15a97d4..6aa678b 100644
  press events when the button is held down. It takes two
  optional parameters:
  
-@@ -1696,7 +1696,7 @@ If you want to permanently unload it add the following line to
+@@ -1752,7 +1752,7 @@ If you want to permanently unload it add the following line to
  .fi
  .PP
  Next you have to load the uinput kernel module which allows
@@ -163,7 +163,7 @@ index 15a97d4..6aa678b 100644
  joydev module handles the \*(T<\fI/dev/input/jsX\fR\*(T>
  devices:
  .PP
-@@ -1716,7 +1716,7 @@ start the userspace driver with:
+@@ -1772,7 +1772,7 @@ start the userspace driver with:
  \*(T<$ xboxdrv\*(T>
  .fi
  .PP
@@ -172,7 +172,7 @@ index 15a97d4..6aa678b 100644
  should often be enough) start the driver as root via:
  .PP
  .nf
-@@ -1743,7 +1743,7 @@ cases it is recomment to change the triggers to regular buttons via:
+@@ -1799,7 +1799,7 @@ cases it is recomment to change the triggers to regular buttons via:
  .fi
  .SS "USING MULTIPLE CONTROLLER"
  If you want to use multiple wired controllers you need to start
@@ -181,7 +181,7 @@ index 15a97d4..6aa678b 100644
  argument to select the appropriate controller like this:
  .PP
  .nf
-@@ -1798,7 +1798,7 @@ can limit which gamepad gets assigned to which slot with
+@@ -1854,7 +1854,7 @@ can limit which gamepad gets assigned to which slot with
  the \*(T<\fB\-\-match\fR\*(T> option.
  .PP
  Note that xboxdrv will create the virtual uinput devices on
@@ -190,7 +190,7 @@ index 15a97d4..6aa678b 100644
  plug in gamepads even after a game or an application like XBMC
  has already been launched and still have it all function
  properly. 
-@@ -1868,7 +1868,7 @@ configuration in a game is most often not helpful, since you won't see
+@@ -1924,7 +1924,7 @@ configuration in a game is most often not helpful, since you won't see
  the true cause beyond endless layers of abstraction between you and
  the actual events. Luckily there are a few tools you can use to test,
  all of these are command line based and it is recomment that you get
@@ -199,7 +199,7 @@ index 15a97d4..6aa678b 100644
  .SS EVTEST
  evtest lets you read raw input events from \*(T<\fI/dev/input/eventX\fR\*(T>. The
  event devices are the very core of all event handling, things like the
-@@ -2150,7 +2150,7 @@ If you have success with that, send a patch
+@@ -2206,7 +2206,7 @@ If you have success with that, send a patch
  to <\*(T<grumbel at gmail.com\*(T>>, if not, contact me too, I
  might be able to provide additional help.
  .PP
@@ -208,7 +208,7 @@ index 15a97d4..6aa678b 100644
  enforce a USB device as well as a controller type an bypass any auto
  detection.
  .SS "\(dqUNKNOWN DATA: BYTES: 3 DATA: ...\(dq"
-@@ -2293,7 +2293,7 @@ And insert the following lines:
+@@ -2349,7 +2349,7 @@ And insert the following lines:
  .fi
  .SS "PERMANENT WORKAROUND BY DISABLING DEVICE AUTO DETECTION"
  A fourth workaround involved disabling the autodetection of Xorg

-- 
xboxdrv packaging

