The linux kernel (as of 3.13) does not recognize them as an ALPS touchpad, and they end up being recognized only as a PS/2 mouse. For this reason there is no scrolling, no middle button emulation, no two finger recognition, etc. I have a DELL Inspiron 17R SE 7720 Laptop and the Alps touchpad is not detected as a touchpad. I tried the psmouse-alps-dst-1.0.tbz and the. Products; Solutions & Services; Support; Community; Browse Community. Download Linux Drivers that are unavailable on Dell Support. C2665dnf Linux driver 64bit.
1.1. Introduction¶
Currently the ALPS touchpad driver supports seven protocol versions in use byALPS touchpads, called versions 1, 2, 3, 4, 5, 6, 7 and 8.
Since roughly mid-2010 several new ALPS touchpads have been released andintegrated into a variety of laptops and netbooks. These new touchpadshave enough behavior differences that the alps_model_data definitiontable, describing the properties of the different versions, is no longeradequate. The design choices were to re-define the alps_model_datatable, with the risk of regression testing existing devices, or isolatethe new devices outside of the alps_model_data table. The latter designchoice was made. The new touchpad signatures are named: 'Rushmore','Pinnacle', and 'Dolphin', which you will see in the alps.c code.For the purposes of this document, this group of ALPS touchpads willgenerically be called 'new ALPS touchpads'.
We experimented with probing the ACPI interface _HID (Hardware ID)/_CID(Compatibility ID) definition as a way to uniquely identify thedifferent ALPS variants but there did not appear to be a 1:1 mapping.In fact, it appeared to be an m:n mapping between the _HID and actualhardware type.
1.2. Detection¶
All ALPS touchpads should respond to the 'E6 report' command sequence:E8-E6-E6-E6-E9. An ALPS touchpad should respond with either 00-00-0A or00-00-64 if no buttons are pressed. The bits 0-2 of the first byte will be 1sif some buttons are pressed.
If the E6 report is successful, the touchpad model is identified using the 'E7report' sequence: E8-E7-E7-E7-E9. The response is the model signature and ismatched against known models in the alps_model_data_array.
For older touchpads supporting protocol versions 3 and 4, the E7 reportmodel signature is always 73-02-64. To differentiate between theseversions, the response from the 'Enter Command Mode' sequence must beinspected as described below.
The new ALPS touchpads have an E7 signature of 73-03-50 or 73-03-0A butseem to be better differentiated by the EC Command Mode response.
1.3. Command Mode¶
Protocol versions 3 and 4 have a command mode that is used to read and writeone-byte device registers in a 16-bit address space. The command sequenceEC-EC-EC-E9 places the device in command mode, and the device will respondwith 88-07 followed by a third byte. This third byte can be used to determinewhether the devices uses the version 3 or 4 protocol.
To exit command mode, PSMOUSE_CMD_SETSTREAM (EA) is sent to the touchpad.
While in command mode, register addresses can be set by first sending aspecific command, either EC for v3 devices or F5 for v4 devices. Then theaddress is sent one nibble at a time, where each nibble is encoded as acommand with optional data. This encoding differs slightly between the v3 andv4 protocols.
Once an address has been set, the addressed register can be read by sendingPSMOUSE_CMD_GETINFO (E9). The first two bytes of the response contains theaddress of the register being read, and the third contains the value of theregister. Registers are written by writing the value one nibble at a timeusing the same encoding used for addresses.
For the new ALPS touchpads, the EC command is used to enter commandmode. The response in the new ALPS touchpads is significantly different,and more important in determining the behavior. This code has beenseparated from the original alps_model_data table and put in thealps_identify function. For example, there seem to be two hardware initsequences for the 'Dolphin' touchpads as determined by the second byteof the EC response.
1.4. Packet Format¶
In the following tables, the following notation is used:
?'s can have different meanings on different models, such as wheel rotation,extra buttons, stick buttons on a dualpoint, etc.
1.5. PS/2 packet format¶
Note that the device never signals overflow condition.
For protocol version 2 devices when the trackpoint is used, and no fingersare on the touchpad, the M R L bits signal the combined status of both thepointingstick and touchpad buttons.
1.6. ALPS Absolute Mode - Protocol Version 1¶1.7. ALPS Absolute Mode - Protocol Version 2¶
Protocol Version 2 DualPoint devices send standard PS/2 mouse packets forthe DualPoint Stick. The M, R and L bits signal the combined status of boththe pointingstick and touchpad buttons, except for Dell dualpoint deviceswhere the pointingstick buttons get reported separately in the PSM, PSRand PSL bits.
1.8. Dualpoint device -- interleaved packet format¶
Devices which use the interleaving format normally send standard PS/2 mousepackets for the DualPoint Stick + ALPS Absolute Mode packets for thetouchpad, switching to the interleaved packet format when both the stick andthe touchpad are used at the same time.
1.9. ALPS Absolute Mode - Protocol Version 3¶
ALPS protocol version 3 has three different packet formats. The first two areassociated with touchpad events, and the third is associated with trackstickevents.
The first type is the touchpad position packet:
Note that for some devices the trackstick buttons are reported in this packet,and on others it is reported in the trackstick packets.
The second packet type contains bitmaps representing the x and y axes. In thebitmaps a given bit is set if there is a finger covering that position on thegiven axis. Thus the bitmap packet can be used for low-resolution multi-touchdata, although finger tracking is not possible. This packet also encodes thenumber of contacts (f1 and f0 in the table below):
This packet only appears after a position packet with the mt bit set, andusually only appears when there are two or more contacts (althoughoccasionally it's seen with only a single contact).
The final v3 packet type is the trackstick packet:
TP means Tap SW status when tap processing is enabled or Press status when pressprocessing is enabled. SW means scroll up when 4 buttons are available.
1.10. ALPS Absolute Mode - Protocol Version 4¶
Protocol version 4 has an 8-byte packet format:
The last two bytes represent a partial bitmap packet, with 3 full packetsrequired to construct a complete bitmap packet. Once assembled, the 6-bytebitmap packet has the following format:
There are several things worth noting here.
So far no v4 devices with tracksticks have been encountered.
1.11. ALPS Absolute Mode - Protocol Version 5¶
This is basically Protocol Version 3 but with different logic for packetdecode. It uses the same alps_process_touchpad_packet_v3 call with aspecialized decode_fields function pointer to correctly interpret thepackets. This appears to only be used by the Dolphin devices.
For single-touch, the 6-byte packet format is:
For mt, the format is:
1.12. ALPS Absolute Mode - Protocol Version 6¶
For trackstick packet, the format is:
For touchpad packet, the format is:
(v6 touchpad does not have middle button)
1.13. ALPS Absolute Mode - Protocol Version 7¶
For trackstick packet, the format is:
For touchpad packet, the format is:
1.14. ALPS Absolute Mode - Protocol Version 8¶
Spoken by SS4 (73 03 14) and SS5 (73 03 28) hardware.
The packet type is given by the APD field, bits 4-5 of byte 3.
Touchpad packet (APD = 0x2):
SWM, SWR, SWL: Middle, Right, and Left button states
Touchpad 1 Finger packet (APD = 0x0):
TAPF: ???LFB: ???
Dell Alps Touchpad Driver Vista
Touchpad 2 Finger packet (APD = 0x1):
Alps Touchpad Driver Windows
CONT: A 3-or-4 Finger packet is to follow
Alps Touchpad Driver Windows 7 64
Touchpad 3-or-4 Finger packet (APD = 0x3):
Alps Touchpad Driver Linux
OVF: 5th finger detected
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |