# Collection of quirks and blacklist/whitelists for specific devices.


# Accelerometer device, posts data through ABS_X/ABS_Y, making X unusable
# http://bugs.freedesktop.org/show_bug.cgi?id=22442 
Section "InputClass"
        Identifier "ThinkPad HDAPS accelerometer blacklist"
        MatchProduct "ThinkPad HDAPS accelerometer data"
        Option "Ignore" "on"
EndSection

# https://bugzilla.redhat.com/show_bug.cgi?id=523914
# Mouse does not move in PV Xen guest
# Explicitly tell evdev to not ignore the absolute axes.
Section "InputClass"
        Identifier "Xen Virtual Pointer axis blacklist"
        MatchProduct "Xen Virtual Pointer"
        Option "IgnoreAbsoluteAxes" "off"
        Option "IgnoreRelativeAxes" "off"
EndSection

# https://bugzilla.redhat.com/show_bug.cgi?id=612140
# please make Evoluent VerticalMouse 3 work out of the box
# Button mapping on this mouse is quirky
Section "InputClass"
	Identifier "Evoluent VerticalMouse 3"
        MatchProduct "Evoluent VerticalMouse 3"
        # Sets following configuration:
        # top button:    left
        # middle button: middle
        # bottom button: right
        # wheel click:   middle
        # thumb button:  8 (back)
	Option "ButtonMapping" "1 2 2 4 5 6 7 3 8"
EndSection


# https://bugs.freedesktop.org/show_bug.cgi?id=55867
# Bug 55867 - Doesn't know how to tag XI_TRACKBALL
Section "InputClass"
        Identifier "Tag trackballs as XI_TRACKBALL"
        MatchProduct "trackball"
        MatchDriver "evdev"
        Option "TypeName" "TRACKBALL"
EndSection

# https://bugs.freedesktop.org/show_bug.cgi?id=62831
# Bug 62831 - Mionix Naos 5000 mouse detected incorrectly
Section "InputClass"
        Identifier "Tag Mionix Naos 5000 mouse XI_MOUSE"
        MatchProduct "La-VIEW Technology Naos 5000 Mouse"
        MatchDriver "evdev"
        Option "TypeName" "MOUSE"
EndSection

# synaptics resolution and axis dimensions are not representative of the
# actual device dimensions, partially because what the kernel exports as
# axis range is the what "fingers of typical size are used on TouchPads
# mounted in typical bezel" produce (synaptics interfacing guide, p 23).
# Even with the axis ranges corrected to what (my) touchpad actually
# produces, the values are even further off, essentially stopping Y
# movement if the server takes resolution into account.
# So for the sake of my sanity, disable synaptics axis resolution by default
# so the server can take the resolution from good devices and use that
# for adjusting movement
Section "InputClass"
        Identifier "Synaptics resolution set to 0"
        MatchDriver "synaptics"
        Option "VertResolution" "0"
        Option "HorizResolution" "0"
EndSection