public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Pettersson <william.pettersson@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: ALPS touchpad with new Dell not recognised
Date: Wed, 01 Aug 2007 17:46:10 +1000	[thread overview]
Message-ID: <46B03A42.3030708@gmail.com> (raw)

I've got a Dell Vostro 1400 here, which according to the Windows drivers
has an ALPS touchpad that I'm working on.  It has PS/2 pass through,
which means I can move the pointer around.  It also picks up (via
hardware I assume) quick double-taps as click-and-drag.  It however,
doesn't do multi-finger taps for middle and right mouse button.  It also
doesn't do side scrolling, which is the big one for me.

/proc/bus/inputs/devices lists the mouse as
I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio1/input0
S: Sysfs=/class/input/input20
H: Handlers=mouse0 event4
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

I enabled debugging in the alps.c driver.  My touchpad "passes" the E6
test, but the E7 test it returns 0x73, 0x2, 0x50.  I've tried adding a
new model to the alps_model_info structure, with these numbers.
This made it be detected as an "Alps", but the behaviour was very
erratic, and kernel messages talked about the GlidePoint lost sync at
byte 1.

I'm not too familiar with the Alps driver, so I don't know exactly how
the byte0 or mask0 variables affect things.  I tried 0xff and 0xf8 as
they were two common options.

Is anyone familiar with the Alps driver, and able to help me work out
how to get this touchpad working?


William

             reply	other threads:[~2007-08-01  7:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-01  7:46 William Pettersson [this message]
2007-08-04 12:15 ` ALPS touchpad with new Dell not recognised William Pettersson
2007-08-04 13:42   ` Matthew Garrett
2007-08-04 19:05   ` Vojtech Pavlik
2007-08-04 22:45     ` William Pettersson
2007-08-05  8:02       ` Vojtech Pavlik
2007-09-05  4:31       ` Dmitry Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B03A42.3030708@gmail.com \
    --to=william.pettersson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox