* ACPI and the psmouse alps driver
@ 2013-01-25 16:07 dturvene
0 siblings, 0 replies; only message in thread
From: dturvene @ 2013-01-25 16:07 UTC (permalink / raw)
To: linux-input
While I'm thinking of it, in the my last alps driver dkms, I put in an
ACPI interface to uniquely detect the touchpad type. After spending a
good couple of days figuring out the ACPI spec and this mysterious _HID
(hardware id) and _CID (compatibility id) as it relates to how ALPS
identifies its touchpads, I can confirm Linus' quote "ACPI is a complete
design disaster in every way. But we're kind of stuck with it." Some
ALPS touchpads have different _HID values. Some have the same _HID but
different behavior.
As far as I can tell ACPI has varying degrees of usefulness based on the
h/w manufacturer. The ALPS MS Windows drivers appear to use ACPI to
figure out if the touchpad is, in fact, from ALPS and then a complicated
series of proprietary retrievals to figure out the behavior.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-01-25 16:07 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-01-25 16:07 ACPI and the psmouse alps driver dturvene
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).