[SCM] xboxdrv packaging branch, master, updated. debian/0.8.0-1-82-g1850f32

Sat Aug 20 09:31:06 UTC 2011

The following commit has been merged in the master branch:
commit fe638e0c29f5040f2aa04a2fc91c821e5b9157c9
Author: Andrey Rahmatullin <wrar at wrar.name>
Date:   Sat Aug 6 18:53:58 2011 +0600

    Update fix-xboxdrv-manpage.patch for 0.8.1.
    
    Signed-off-by: Andrey Rahmatullin <wrar at wrar.name>

diff --git a/debian/patches/fix-xboxdrv-manpage.patch b/debian/patches/fix-xboxdrv-manpage.patch
index b0f6492..0ebf7d7 100644
--- a/debian/patches/fix-xboxdrv-manpage.patch
+++ b/debian/patches/fix-xboxdrv-manpage.patch
@@ -1,11 +1,11 @@
 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: https://github.com/Grumbel/xboxdrv/pull/7
-Last-Update: 2011-07-16
+Forwarded: no
+Last-Update: 2011-08-06
 
 diff --git a/doc/xboxdrv.1 b/doc/xboxdrv.1
-index 5df6a1f..b1beb4a 100644
+index 15a97d4..6aa678b 100644
 --- a/doc/xboxdrv.1
 +++ b/doc/xboxdrv.1
 @@ -56,7 +56,7 @@ for more information.
@@ -17,7 +17,7 @@ index 5df6a1f..b1beb4a 100644
  Print the version number and exit.
  .TP 
  \*(T<\fB\-v\fR\*(T>, \*(T<\fB\-\-verbose\fR\*(T>
-@@ -140,8 +140,8 @@ files. Regular key/value pairs must go into the
+@@ -144,8 +144,8 @@ files. Regular key/value pairs must go into the
  [xboxdrv] section. '#' and ';' can be used for comments.
  Key names have for most part the same name as command
  line options. Command line options that take a list of
@@ -28,38 +28,16 @@ index 5df6a1f..b1beb4a 100644
  section for better readability.
  
  The \*(T<\fIexamples/\fR\*(T> directory contains
-@@ -348,7 +348,7 @@ events from that device. This is done to avoid confusing
- applications, as otherwise an app would receive every
- event twice, once from the original device and once from
- the virtual xboxdrv one. In some cases this behaviour is
--undesired, such when mapping only an other wise
-+undesired, such when mapping only an otherwise
- unhandled subset of keys of an device, i.e. mapping the
- multimedia keys on a keyboard, so this option turns the
- grab off.
-@@ -530,10 +530,10 @@ for developers only and will dump raw headset data, not .wav
- files.
+@@ -334,7 +334,7 @@ xpad module loaded and want to use xboxdrv without
+ unloading it.
  .TP 
- \*(T<\fB\-\-headset\fR\*(T>
--Enable headset support and dump incomming data to stdout.
-+Enable headset support and dump incoming data to stdout.
- .TP 
- \*(T<\fB\-\-headset\-dump\fR\*(T> \fIFILE\fR
--Enable headset support and dump incomming data to FILE.
-+Enable headset support and dump incoming data to FILE.
- .TP 
- \*(T<\fB\-\-headset\-play\fR\*(T> \fIFILE\fR
- Enable headset support and send FILE to the headset for playback.
-@@ -596,7 +596,7 @@ Match controllers that have the
- given USB idProduct.
- .TP 
- property=\fIPROPERTY\fR:\fIVALUE\fR
--Match against an arbitary udev property, with
-+Match against an arbitrary udev property, with
- name \fIPROPERTY\fR and
- value \fIVALUE\fR.
- .TP 
-@@ -724,7 +724,7 @@ T}
+ \*(T<\fB\-\-generic\-usb\-spec\fR\*(T> \fINAME=VALUE,...\fR
+-Allows to specify from which
++Allows one to specify from which
+ 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}
  T{
  lt(7), rt(8)
  T}	T{
@@ -68,7 +46,7 @@ index 5df6a1f..b1beb4a 100644
  T}
  T{
  tl, tr
-@@ -734,7 +734,7 @@ T}
+@@ -777,7 +777,7 @@ T}
  T{
  du(up), dd(down), dl(left), dr(right)
  T}	T{
@@ -77,7 +55,7 @@ index 5df6a1f..b1beb4a 100644
  T}
  T{
  green, red, yellow, blue, orange
-@@ -746,7 +746,7 @@ T}
+@@ -789,7 +789,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
@@ -86,7 +64,7 @@ index 5df6a1f..b1beb4a 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:
  
-@@ -789,7 +789,7 @@ as autofire while another one, emitting the same signal, acts normally.
+@@ -832,7 +832,7 @@ as autofire while another one, emitting the same signal, acts normally.
  .fi
  .TP 
  \*(T<\fB\-\-axis\-sensitivty \fR\*(T>\fIAXIS=SENSITIVITY\fR,...
@@ -95,7 +73,7 @@ index 5df6a1f..b1beb4a 100644
  
  .nf
  \*(T<$ xboxdrv \-\-axis\-sensitivty X1=\-1.0,Y1=\-1.0\*(T>
-@@ -798,7 +798,7 @@ The sensitive of an axis can be adjusted via --axis-sensitivty:
+@@ -841,7 +841,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
@@ -104,7 +82,7 @@ index 5df6a1f..b1beb4a 100644
  will generally give good results, everything beyond that
  won't be of much practical use.
  
-@@ -881,7 +881,7 @@ Will give you controls that are relative to your
+@@ -924,7 +924,7 @@ Will give you controls that are relative to your
  character instead of your viewpoint.
  .TP 
  \*(T<\fB\-\-four\-way\-restrictor\fR\*(T>
@@ -113,7 +91,7 @@ index 5df6a1f..b1beb4a 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
-@@ -1017,7 +1017,7 @@ switch this behaviour off.
+@@ -1060,7 +1060,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
@@ -122,7 +100,7 @@ index 5df6a1f..b1beb4a 100644
  .TP 
  \*(T<\fB\-\-device\-names TYPE.SLOT=NAME,...\fR\*(T>
  Changes the descriptive name the device will
-@@ -1032,7 +1032,7 @@ matches everything.
+@@ -1075,7 +1075,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
@@ -131,16 +109,34 @@ index 5df6a1f..b1beb4a 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
-@@ -1138,7 +1138,7 @@ event. The final determination of which device gets
- handled as what will be done by the Kernel or Xorg
- depending on what events a device provides. 
- 
--An example configuration makeing use of device_id would look like this:
-+An example configuration making use of device_id would look like this:
+@@ -1270,7 +1270,7 @@ is \fIVALUE\fR * axis_state.
+ gives the number of milisecond to pass before the event
+ is fired again (default: 5).
  
+-The value of -1 has a special meaning, it will result in
++The value of \-1 has a special meaning, it will result in
+ 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
+ event handler. What kind of arguments an event handler allows
+ depends on the event handler.
+ .PP
+-There is also a shorthand form of specifing event handlers by
++There is also a shorthand form of specifying event handlers by
+ just writing:
+ .PP
  .nf
- \*(T<xboxdrv \-s \e
-@@ -1272,7 +1272,7 @@ is \fIVALUE\fR * axis_state.
+@@ -1427,7 +1427,7 @@ will default to 'backward'.
+ See \*(T<\fBcycle\-key\-named\fR\*(T> for a full example.
+ .TP 
+ \*(T<\fBexec\fR\*(T>
+-The exec button handler allows to launch an application
++The exec button handler allows one to launch an application
+ when the button was pressed. An example would look like
+ this:
+ 
+@@ -1506,7 +1506,7 @@ is \fIVALUE\fR * axis_state.
  gives the number of milisecond to pass before the event
  is fired again (default: 5).
  
@@ -149,7 +145,7 @@ index 5df6a1f..b1beb4a 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,
-@@ -1324,7 +1324,7 @@ when it is not pressed and in unpressed state when it is
+@@ -1561,7 +1561,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
@@ -158,7 +154,7 @@ index 5df6a1f..b1beb4a 100644
  press events when the button is held down. It takes two
  optional parameters:
  
-@@ -1445,7 +1445,7 @@ If you want to permanently unload it add the following line to
+@@ -1696,7 +1696,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
@@ -167,7 +163,7 @@ index 5df6a1f..b1beb4a 100644
  joydev module handles the \*(T<\fI/dev/input/jsX\fR\*(T>
  devices:
  .PP
-@@ -1465,7 +1465,7 @@ start the userspace driver with:
+@@ -1716,7 +1716,7 @@ start the userspace driver with:
  \*(T<$ xboxdrv\*(T>
  .fi
  .PP
@@ -176,7 +172,7 @@ index 5df6a1f..b1beb4a 100644
  should often be enough) start the driver as root via:
  .PP
  .nf
-@@ -1492,7 +1492,7 @@ cases it is recomment to change the triggers to regular buttons via:
+@@ -1743,7 +1743,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
@@ -185,7 +181,7 @@ index 5df6a1f..b1beb4a 100644
  argument to select the appropriate controller like this:
  .PP
  .nf
-@@ -1547,7 +1547,7 @@ can limit which gamepad gets assigned to which slot with
+@@ -1798,7 +1798,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
@@ -194,7 +190,7 @@ index 5df6a1f..b1beb4a 100644
  plug in gamepads even after a game or an application like XBMC
  has already been launched and still have it all function
  properly. 
-@@ -1617,7 +1617,7 @@ configuration in a game is most often not helpful, since you won't see
+@@ -1868,7 +1868,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
@@ -203,8 +199,8 @@ index 5df6a1f..b1beb4a 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
-@@ -1899,7 +1899,7 @@ If you have success with that, send a patch
- to <\*(T<grumbel at gmx.de\*(T>>, if not, contact me too, I
+@@ -2150,7 +2150,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
 -As an alternative you can also use the --device and --type option to
@@ -212,7 +208,7 @@ index 5df6a1f..b1beb4a 100644
  enforce a USB device as well as a controller type an bypass any auto
  detection.
  .SS "\(dqUNKNOWN DATA: BYTES: 3 DATA: ...\(dq"
-@@ -2042,7 +2042,7 @@ And insert the following lines:
+@@ -2293,7 +2293,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

