#10417 NORM Future : Enable Synaptics mode for CL1A/CL1B/CL1C touchpad

[Zarro Boogs per Child]

#10417: Enable Synaptics mode for CL1A/CL1B/CL1C touchpad
---------------------------------------+------------------------------------
           Reporter:  martin.langhoff  |       Owner:  cjb           
               Type:  enhancement      |      Status:  new           
           Priority:  normal           |   Milestone:  Future Release
          Component:  distro           |     Version:  not specified 
         Resolution:                   |    Keywords:                
        Next_action:  never set        |    Verified:  0             
Deployment_affected:                   |   Blockedby:                
           Blocking:                   |  
---------------------------------------+------------------------------------

Comment(by dsd):

 Procedure for Richard:

 Target hardware is XO-1.5 with synaptics touchpad. To identify this, grep
 Synaptics /proc/bus/input/devices

 Start from any recent 11.3.0 build such as
 http://build.laptop.org/11.3.0/os8/xo-1.5/os8.zd4


 Install test kernel:
 {{{
 rpm -Uvh
 http://dev.laptop.org/~dsd/20111004/kernel-2.6.35.13_xo1.5-20111004.1557.olpc.1d237ac.i586.rpm
 rsync -av --delete-before /boot/ /bootpart/boot/
 reboot
 }}}

 Check that synaptics kernel driver is enabled:
 {{{
 grep SynPS /proc/bus/input/devices
 }}}

 If you notice the mouse going crazy in X, or you have difficulty typing
 the above command because they keyboard isn't working right, that's
 equally valid evidence that the synaptics kernel driver has kicked in :)

 now install http://kojipkgs.fedoraproject.org/packages/xorg-x11-drv-
 synaptics/1.3.0/1.fc14/i686/xorg-x11-drv-synaptics-1.3.0-1.fc14.i686.rpm
 and reboot again

 Now the mouse should be fine again, but you should experience problems
 typing while using the mouse (or simply having fingers nearby). This is
 the problem to then diagnose with the EC hookup.

 If you want to see the kernels view of i8042 interrupts and data:
 {{{
 echo 1 > /sys/module/i8042/parameters/debug
 }}}

 The output lines will be e.g.
 {{{
 32 <- i8042 (interrupt, 1, 12)
 }}}

 In the above example, 32 is the byte read from I8042_DATA_REG. 1 is the
 port number and 12 is the IRQ. Mouse stuff comes in on IRQ 12 and keyboard
 on IRQ 1.

 This info is logged in dmesg by default. If you enable log messages to be
 sent over serial (with e.g.  dmesg -n 8), the huge amount of data sent by
 synaptics pad in this mode causes such a slowdown that problems occur
 (failed resyncs etc).

 I find it easier to have it just logging to dmesg internally, then
 reproduce the issue, then examine dmesg logs.

 In a couple of tests I just made, typing the characters "myna" while
 moving the mouse, the "n" is the only character that hit the screen.
 According to the logs, there was a huge amount of mouse data, then at the
 very end Linux received the 0x31 'n' make code once, then the 0xb1 'n'
 break code 7 times, with no sign of the other keys that I pressed.

-- 
Ticket URL: <http://dev.laptop.org/ticket/10417#comment:16>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system