From: Alex Chiang <achiang@hp.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, tiwai@suse.de
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-input@vger.kernel.org
Subject: Re: synaptics touchpad doesn't click
Date: Mon, 14 Dec 2009 20:41:27 -0700 [thread overview]
Message-ID: <20091215034127.GC587@ldl.fc.hp.com> (raw)
In-Reply-To: <20091214173450.GB2373@core.coreip.homeip.net>
Hi Dmitry, Takashi,
* Dmitry Torokhov <dmitry.torokhov@gmail.com>:
> Hi Alex,
>
> On Sun, Dec 13, 2009 at 06:48:28PM -0700, Alex Chiang wrote:
> > Hi Dmitry,
> >
> > I just got a shiny new piece of hardware (HP Envy 15) with a
> > Synaptics touchpad, and I can't seem to make the touchpad work
> > correctly. In this version of the touchpad, there are actually
> > two physical buttons underneath the pad. In essence, this is a
> > touchpad that you can click too.
> >
> > I can't get the clicking to work. Of course, I can tap to click,
> > but lacking access to the physical buttons means that I can't
> > right-click.
> >
> > Currently, I'm not sure if this is a driver issue or perhaps
> > something higher up the stack, perhaps in X or maybe pilot error.
> > ;)
> >
> > Distro is Ubuntu Karmic, kernel is latest upstream last pulled on
> > 13 Dec.
> >
> > Would like some pointers on how to get started debugging.
> >
> > Thanks,
> > /ac
> >
> > dmesg snip:
> > Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> > brd: module loaded
> > loop: module loaded
> > input: Macintosh mouse button emulation as /devices/virtual/input/input3
> > [...]
> > Synaptics Touchpad, model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd04771/0xe40000
> > input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10
> >
>
> Hmm, that's the new Synaptics "clickpad"... Takashi Iwai just posted a
> coupleof patches for it on the input mailing list.
I can't respond to that thread directly because I'm not a
subscriber and can't find the message-id, so just responding
here.
Thanks, I did grab Takashi's patches and verify that they work
for me. I tested the separated patches, not the v2 combined
patch, although it doesn't make any difference based on visual
inspection of v2.
If you want, you can add my:
Tested-by: Alex Chiang <achiang@hp.com>
Thanks!
/ac
next prev parent reply other threads:[~2009-12-15 3:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 1:48 synaptics touchpad doesn't click Alex Chiang
2009-12-14 17:34 ` Dmitry Torokhov
2009-12-15 3:41 ` Alex Chiang [this message]
2009-12-15 6:26 ` Dmitry Torokhov
2009-12-15 6:40 ` Takashi Iwai
2009-12-15 7:33 ` Dmitry Torokhov
2009-12-15 7:41 ` Takashi Iwai
2009-12-15 8:25 ` Dmitry Torokhov
2009-12-15 10:19 ` Takashi Iwai
2009-12-15 10:41 ` Takashi Iwai
2009-12-16 1:05 ` Alex Chiang
2009-12-16 2:59 ` Dmitry Torokhov
2009-12-16 6:50 ` Takashi Iwai
2009-12-16 6:56 ` Dmitry Torokhov
2009-12-16 7:14 ` Takashi Iwai
2009-12-16 8:23 ` Dmitry Torokhov
2009-12-16 9:17 ` Takashi Iwai
2009-12-16 17:24 ` Dmitry Torokhov
2009-12-16 17:32 ` Takashi Iwai
2009-12-16 7:16 ` Takashi Iwai
2009-12-16 6:52 ` Alex Chiang
2009-12-16 7:03 ` Dmitry Torokhov
2009-12-16 7:11 ` Takashi Iwai
2009-12-16 8:20 ` Dmitry Torokhov
2009-12-16 9:14 ` Takashi Iwai
2009-12-16 17:31 ` Alex Chiang
2009-12-16 17:42 ` 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=20091215034127.GC587@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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