From: David B Harris <dbharris@eelf.ddts.net>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: Adesso SmartCat USB Synaptics touchpad
Date: Wed, 02 Jun 2010 16:06:42 -0400 [thread overview]
Message-ID: <1275509202.32129.0.camel@willow.eelf.ddts.net> (raw)
In-Reply-To: <20100602072947.GF3713@core.coreip.homeip.net>
Hey, thanks for the response. I was concerned that that was the problem.
On Wed, 2010-06-02 at 00:29 -0700, Dmitry Torokhov wrote:
> On Mon, May 31, 2010 at 07:48:48PM -0400, David B Harris wrote:
> > Hello again all,
> >
> > This time we have an "Adesso Smart Cat USB" touchpad, which is
> > unrecognized (I believe) by the kernel.
> >
> > Here's the relevant /proc/bus/input/devices entry:
> >
> > I: Bus=0003 Vendor=0488 Product=0022 Version=0100
> > N: Name="Cirque Corporation USB GlidePoint"
> > P: Phys=usb-0000:00:02.1-10.4.2/input0
> > S: Sysfs=/devices/pci0000:00/0000:00:02.1/usb1/1-10/1-10.4/1-10.4.2/1-10.4.2:1.0/input/input6
> > U: Uniq=
> > H: Handlers=mouse2 event6
> > B: EV=1f
> > B: KEY=70000 0 0 0 0
> > B: REL=103
> > B: ABS=70000000000
> > B: MSC=10
> >
> > Can anybody provide some pointers on how to start tracking this down?
> > i8032.debug seems to do little.
> >
>
> Right, because it is USB touchpad and not PS/2 one. It might be driver
> by an out-of-tree Synaptics USB driver.
>
> *sigh* Yes, I want to merge the driver, I even have hardware to test
> (Tejun sent me a device), what I don't have is time to clean it up :(
>
--
Arguing with an engineer is like wrestling with a pig in mud.
After a while, you realise the pig is enjoying it.
OpenPGP v4 key ID: 4096R/59DDCB9F
Fingerprint: CC53 F124 35C0 7BC2 58FE 7A3C 157D DFD9 59DD CB9F
Retrieve from subkeys.pgp.net
prev parent reply other threads:[~2010-06-02 20:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 23:48 Adesso SmartCat USB Synaptics touchpad David B Harris
2010-06-02 7:29 ` Dmitry Torokhov
2010-06-02 20:06 ` David B Harris [this message]
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=1275509202.32129.0.camel@willow.eelf.ddts.net \
--to=dbharris@eelf.ddts.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@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;
as well as URLs for NNTP newsgroup(s).