Bug 35209 - xorg.conf(5) man page: INPUTDEVICE SECTION is incomplete
Summary: xorg.conf(5) man page: INPUTDEVICE SECTION is incomplete
Alias: None
Product: xorg
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 7.6 (2010.12)
Hardware: All All
: medium enhancement
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
Depends on:
Reported: 2011-03-11 04:41 UTC by Vincent Lefevre
Modified: 2011-10-15 15:58 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Vincent Lefevre 2011-03-11 04:41:20 UTC
INPUTDEVICE SECTION in xorg.conf(5) man page contains:

       The config file may have multiple InputDevice sections.   Recent  X
       servers employ input hotplugging to add input devices, with the HAL
       backend being the default backend for X servers since  1.4.  It  is
       usually  not  necessary  to  provide  InputDevice  sections  in the
       xorg.conf if hotplugging is enabled.

By "it is usually not necessary", one may assume that one can still add them for additional options. However, if hotplugging is enabled, such options will be ignored. The description should add something like:

  If hotplugging is enabled and options need to be added, an InputClass section should be used instead of an InputDevice section.

and perhaps replace "it is usually not necessary" by "it is usually incorrect".
Comment 1 Peter Hutterer 2011-03-15 15:09:48 UTC
Comment 2 Jeremy Huddleston Sequoia 2011-10-06 09:57:59 UTC
commit 6f46ae3c69c48f389560af1491ed1729ba45866f
Author: Peter Hutterer <peter.hutterer@who-t.net>
Date:   Tue Mar 15 13:20:03 2011 +1000

    man: list the drivers that are ignored when hotplugging (#35209)
    X.Org Bug 35209 <http://bugs.freedesktop.org/show_bug.cgi?id=35209>
    Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
    Reviewed-by: Cyril Brulebois <kibi@debian.org>
    Reviewed-by: Julien Cristau <jcristau@debian.org>

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.