xfree86: Make InputClass docs and comments match reality

Drivers and options specified in InputClass sections work on a "first
match wins" strategy. Let's be consistent when documenting it.

Signed-off-by: Dan Nicholson <dbn.lists@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
Dan Nicholson 2010-02-10 15:36:44 +10:00 committed by Peter Hutterer
parent a34812b090
commit 67bc278a51
2 changed files with 4 additions and 4 deletions

View File

@ -538,9 +538,9 @@ InputClassMatches(XF86ConfInputClassPtr iclass, InputAttributes *attrs)
}
/*
* Merge in any InputClass configurations. Each InputClass section can
* add to the original device configuration as well as any previous
* InputClass sections.
* Merge in any InputClass configurations. Options in each InputClass
* section have less priority than the original device configuration as
* well as any previous InputClass sections.
*/
static int
MergeInputClasses(IDevPtr idev, InputAttributes *attrs)

View File

@ -1021,7 +1021,7 @@ The
entry specifies the name of the driver to use for this input device.
After all classes have been examined, the
.RI \*q inputdriver \*q
module from the final
module from the first
.B Driver
entry will be enabled when using the loadable server.
.PP