Provided by: xserver-xorg-input-evdev_1.2.0-1ubuntu2_i386 bug

NAME

       evdev - Generic Linux input driver

SYNOPSIS

       Section "InputDevice"
         Identifier "devname"
         Driver "evdev"
         Option "Device"   "devpath"
         ...
       EndSection

DESCRIPTION

       evdev  is  an  Xorg input driver for Linux’s generic event devices.  It
       therefore supports all input  devices  that  the  kernel  knows  about,
       including most mice and keyboards.

       The  evdev  driver  can  serve  as  both a pointer and a keyboard input
       device, and may be used as both the core keyboard and the core pointer.
       Multiple  input  devices  are  supported  by multiple instances of this
       driver.

SUPPORTED HARDWARE

       In general, any input device that the kernel has a driver  for  can  be
       accessed  through the evdev driver.  See the Linux kernel documentation
       for a complete list.

CONFIGURATION DETAILS

       Please refer to xorg.conf(5) for general configuration details and  for
       options  that  can  be  used with all input drivers.  This section only
       covers configuration details specific to this driver.

BASIC CONFIGURATIONS

       Most users of this  driver  will  probably  be  quite  happy  with  the
       following for all keyboards and mice:

       Section "InputDevice"
         Identifier "keyboard"
         Driver "evdev"
         Option "Device"  "/dev/input/by-path/..."
         ...
       EndSection

ADVANCED OPTIONS

   DEVICE SPECIFICATION
       Option "Path" "string"

       Option "Device" "string"
              Specifies  the  device  node  through  which  the  device can be
              accessed.  You might want to use the  more  persistent  symlinks
              provided in /dev/input/by-id or /dev/input/by-path.
              This parameter is mandatory.

       Option "Mode" "mode"
              This selects the default mode for the device.
              Valid values are "absolute" and "relative".
              This  can  be  set at run time per actual device with the xinput
              utility.

   RELATIVE AXIS CONFIGURATION
       The relative axis portion of this driver handle all  reported  relative
       axes.
       The  axes are named X, Y, Z, RX, RY, RZ, HWHEEL, DIAL, WHEEL, MISC, 10,
       11, 12, 13, 14, and 15.
       The axes are reported to X as valuators, with the  default  mapping  of
       axes to valuators being the first axes found to the first valuator, the
       second found to the second valuator, and so on, so  that  if  you  have
       axes  X,  Y,  HWHEEL,  and  WHEEL,  you  would have X=0, Y=1, HWHEEL=2,
       WHEEL=3.
       If the driver is reporting core events, valuators 0 and  1  are  always
       mapped to x and y coordinates, respectively.
       The  following  driver Options control the relative axis portion of the
       driver:

       Option "Rel%sMapTo" "string"
              This remaps the axis specified by %s  to  string.   See  Section
              AXIS MAPPING for valid values.

       Option "Rel%sOptions" "string"
              This  sets  some  options for the relative axis specified by %s.
              Valid value is "invert".
              <documentation needed>

   ABSOLUTE AXIS CONFIGURATION
       The absolute axis portion of this driver handles all reported  absolute
       axes.
       The  axes  are named X, Y, Z, RX, RY, RZ, THROTTLE, RUDDER, WHEEL, GAS,
       BRAKE, <11-15>, HAT0X, HAT0Y, HAT1X, HAT1Y, HAT2X, HAT2Y, HAT3X, HAT3Y,
       PRESSURE, TILT_X, TILT_Y, TOOL_WIDTH, VOLUME, <29-39>, MISC, <41-62>.
       The  axes  are  reported to X as valuators, with the default mapping of
       axes to valuators being the first axes found to the first valuator, the
       second  found  to  the  second valuator, and so on, so that if you have
       axes X, Y, TILT_X, and TILT_Y,  you  would  have  X=0,  Y=1,  TILT_X=2,
       TILT_Y=3.
       If  the  driver  is reporting core events, valuators 0 and 1 are always
       mapped to x and y coordinates, respectively.
       The following driver Options control the absolute axis portion  of  the
       driver:

       Option "Abs%sMapTo" "string"
              This  remaps  the  axis  specified by %s to string.  See Section
              AXIS MAPPING for valid values.

       Option "Abs%sOptions" "string"
              This sets some options for the absolute axis specified by %s.
              Valid values are "invert", "use_touch", "mode_auto", "mode_rel".
              <documentation needed>

       Option "AbsoluteTouch" "string"
              <documentation needed>
              Default: DIGI_Touch

   AXIS MAPPING
       The following axis mappings are recognized:

       "RelAxis <axis>"
              Map  the axis to the specified <axis> in relative mode. This can
              be either a number or a name.

       "AbsAxis <axis> <min> <max>"
              Maps the axis to the specified <axis> in absolute mode. This can
              be either a number or a name.

       "Button <button>"
              Maps the button to the button specified with <button>.  This can
              be either a button number or a name.

       "Buttons <button+> <button->"
              Maps the positive axis to the button  specified  with  <button+>
              and  the  negative  axis to the button specified with <button->.
              These can be either button numbers or names.

   BUTTON CONFIGURATION
       At the moment, the button portion of this driver only  handles  buttons
       reported  as mouse buttons, that is from BTN_MOUSE to BTN_JOYSTICK - 1.
       At this time there are no configuration options for buttons.

   KEYBOARD CONFIGURATION
       The keyboard portion of this  driver  handles  all  keys  reported  and
       requires XKB support.
       The  following  driver Options control the relative axis portion of the
       driver:

       Option "XkbRules" "rules"
              specifies which XKB rules  file  to  use  for  interpreting  the
              XkbModel,   XkbLayout,   XkbVariant,  and  XkbOptions  settings.
              Default: "xorg"  for  most  platforms,  but  "xfree98"  for  the
              Japanese PC-98 platforms.

       Option "XkbModel" "modelname"
              specifies the XKB keyboard model name.  Default: "evdev".

       Option "XkbLayout" "layoutname"
              specifies  the  XKB  keyboard  layout name.  This is usually the
              country or language type of the keyboard.  Default: "us".

       Option "XkbVariant" "variants"
              specifies the XKB keyboard variant  components.   These  can  be
              used  to enhance the keyboard layout details.  Default: not set.

       Option "XkbOptions" "options"
              specifies the XKB keyboard option components.  These can be used
              to enhance the keyboard behaviour.  Default: not set.

AUTHORS

       Zephaniah E. Hull.
       Kristian Høgsberg.

SEE ALSO

       Xorg(1), xorg.conf(5), xorgconfig(1), Xserver(1), X(7).