Lines Matching refs:packet

22     4.2 Native relative mode 4 byte packet format
23     4.3 Native absolute mode 4 byte packet format
26     5.2 Native absolute mode 6 byte packet format
27         5.2.1 Parity checking and packet re-synchronization
32     6.2 Native absolute mode 6 byte packet format
37     7.2 Native absolute mode 6 byte packet format
38         7.2.1 Status packet
39         7.2.2 Head packet
40         7.2.3 Motion packet
43     8.2 Native relative mode 6 byte packet format
54 packet. Version 2 seems to be introduced with the EeePC and uses 6 bytes
55 per packet, and provides additional features such as position of two fingers,
56 and width of the touch.  Hardware version 3 uses 6 bytes per packet (and
58 of up to 3 fingers. Hardware version 4 uses 6 bytes per packet, and can
59 combine a status packet with multiple head or motion packets. Hardware version
63 separate packet format. It is also 6 bytes per packet.
107    "2" will turn on packet debugging. For hardware version 1 the default is
110    Turning packet debugging on will make the driver dump every packet
123    calculating a parity bit for the last 3 bytes of each packet. The driver
124    can check these bits and reject any packet that appears corrupted. Using
139    driver will reject any packet that appears corrupted. Using this knob,
207          F: 1 = enable native 4 byte packet mode
241 4.2 Native relative mode 4 byte packet format
299 4.3 Native absolute mode 4 byte packet format
393 5.2 Native absolute mode 6 byte packet format
395 5.2.1 Parity checking and packet re-synchronization
399         SA1= packet[0];
400         A1 = packet[1];
401         B1 = packet[2];
402         SB1= packet[3];
403         C1 = packet[4];
404         D1 = packet[5];
414         if( ((packet[0] & 0x0C) != 0x04) ||
415             ((packet[3] & 0x0f) != 0x02) )
419 In case an error is detected, all the packets are shifted by one (and packet[0] is discarded).
544 6.2 Native absolute mode 6 byte packet format
546 1 and 3 finger touch shares the same 6-byte packet format, except that
553 when number of finger changes, F/W would send "debounce packet" to inform
555 The debouce packet has the following signature:
562 When we encounter this kind of packet, we just ignore it.
611 The packet format is exactly the same for two finger touch, except the hardware
612 sends two 6 byte packets. The first packet contains data for the first finger,
613 the second packet has data for the second finger. So for two finger touch a
630 7.2 Native absolute mode 6 byte packet format
633 Unfortunately, due to PS/2's limited bandwidth, its packet format is rather
637 status packet to indicate how many and which fingers is on touchpad, followed by
638 head packets or motion packets. A head packet contains data of finger id, finger
639 position (absolute x, y values), width, and pressure. A motion packet contains
642 For example, when status packet tells there are 2 fingers on touchpad, then we
645 position, until we receive a status packet.
647 One exception is one finger touch. when a status packet tells us there is only
650 7.2.1 Status packet
685 7.2.2 Head packet
729 7.2.3 Motion packet
787 8.2 Native relative mode 6 byte packet format