xorg.conf.d - InputClass feature request
alberto.milone at canonical.com
Sun Jan 3 01:44:25 PST 2010
On Sunday 03 Jan 2010 06:24:07 you wrote:
> On the other hand, I'd really hope that these types of quirks would be
> handled in the kernel. Looking at the option you've listed above, why
> is the kernel exposing the whole touchpad area when there's a button
> below part of it? Also, what's JumpyCursorThreshold? I don't recall
> seeing that anywhere.
The AreaBottomEdge option is meant to be used with touchpads that have
physical buttons underneath the bottom edge of their surface. For further
details, see bug #21613 on freedesktop. I wouldn't know if the kernel can be
made aware of this specific hardware design.
You can safely ignore the JumpyCursorThreshold option as upstream hasn't
accepted my patch (bug #21614). It's meant to reduce cursor jumpiness on
otherwise unbearably unstable touchpads (e.g. the Dell Mini 10v).
The specific options that I mentioned are not really the point here though.
Different systems could require different settings (other than the ones I
mentions) and DMI matching can help us make things work better (at least as
regards touchpads) when it's either not possible or feasible (think of
deadlines that OEMs and/or distributions have) to fix things in the kernel, in
the X driver, etc.
Note: just to be clear, I'm *not* suggesting that we fill /etc/xorg.conf.d
with a million configuration files instead of fixing things properly. I would
only like to be able to use quirks again.
Sustaining Engineer (system)
Canonical OEM Services
More information about the xorg-devel