[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101214170027.GA11318@core.coreip.homeip.net>
Date: Tue, 14 Dec 2010 09:00:27 -0800
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Jiri Kosina <jkosina@...e.cz>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Synaptics touchpad on Dell Vostro V13
On Tue, Dec 14, 2010 at 03:56:56PM +0100, Jiri Kosina wrote:
> Hi Dmitry,
>
> I have a bugreport about Synaptics touchpad not working as proper
> Synaptics, but only being detected as standard PS/2.
>
> Looking at the i8042.debug output, the device is clearly buggy, as it
> doesn't identify itself by 0x47 when queried:
>
> 91 -> i8042 (command) [58]
> e8 -> i8042 (parameter) [58]
> fa <- i8042 (interrupt, 3, 12) [59]
> 91 -> i8042 (command) [59]
> 00 -> i8042 (parameter) [59]
> fa <- i8042 (interrupt, 3, 12) [59]
> 91 -> i8042 (command) [59]
> e8 -> i8042 (parameter) [59]
> fa <- i8042 (interrupt, 3, 12) [60]
> 91 -> i8042 (command) [60]
> 00 -> i8042 (parameter) [60]
> fa <- i8042 (interrupt, 3, 12) [61]
> 91 -> i8042 (command) [61]
> e8 -> i8042 (parameter) [61]
> fa <- i8042 (interrupt, 3, 12) [61]
> 91 -> i8042 (command) [61]
> 00 -> i8042 (parameter) [61]
> fa <- i8042 (interrupt, 3, 12) [62]
> 91 -> i8042 (command) [62]
> e8 -> i8042 (parameter) [62]
> fa <- i8042 (interrupt, 3, 12) [63]
> 91 -> i8042 (command) [63]
> 00 -> i8042 (parameter) [63]
> fa <- i8042 (interrupt, 3, 12) [64]
> 91 -> i8042 (command) [64]
> e9 -> i8042 (parameter) [64]
> fa <- i8042 (interrupt, 3, 12) [64]
>
> ... and here we time out after approximately 0.5s. nomux doesn't really
> fix it, we start getting a lot of timeouts on i8042 with that.
>
> Apparently the device works with Synaptics driver in Other OS(TM) though.
> Do you have any idea what they might be doing differently so that they
> make the touchpad identify itself properly?
Hi Jiri,
Do you have the device in your possession? If so can you check if the
driver installed in Other OS uses active multiplexing? I think you can
infer whether it does or not by looking at the pointer properties - I
think it would "Synaptics Blah at port X" or something like that...
Also you could try combining nomux with reset and see if it makes any
sense...
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists