Comment 259 for bug 606238

@ Markus and Nicolas

Both of your E6230 systems have the same symptoms so I think it is
systematic. My thoughts:

Problem summary:

The E6230 touchpad has the same signature and command-mode response as
the E6430, so it is detected as a V4 protocol. The initialization
sequence fails about halfway, putting the device in an unknown state.
The psmouse driver completes initialization but the hardware is
unresponsive. Reboot does not reset the touchpad because the driver is
unresponsive. Power cycle resets the device.

Workaround:

The E6430 code fails on the E6230. If Ben's E6230 code is removed from
alps.c your touchpad will default to the defacto 3-byte ps2 mode, which
works but is limited.

Possible Fix Paths:

1. Somehow the E6430 and E6230 must be identified differently (not just
the E7 sequence and command mode response, which are identical) in order
to differentiate the initialization paths. Then the E6230 must be
reverse engineered to capture the desired init sequence and packet
processing.

2. Ben Garami's initialization reverse engineering sequence is not
complete. I know he did not spend a lot of time analyzing it. The init
sequence must be captured for the E6230 and blended with the E6430 hw init.

Does the Dell(Alps) touchpad driver for the E6430 say it supports the
E6230? If so then Ben's sequence is not complete.