LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: linux-input@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	William Pettersson <william.pettersson@gmail.com>
Subject: Re: [BISECTED] Re: psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
Date: Wed, 16 Jan 2008 10:42:42 -0500	[thread overview]
Message-ID: <20080116104024.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <20080115154142.ZZRA012@mailhub.coreip.homeip.net>

On Tue, Jan 15, 2008 at 03:49:12PM -0500, Dmitry Torokhov wrote:
> Hi Vegard,
> 
> On Tue, Jan 15, 2008 at 07:28:38PM +0100, Vegard Nossum wrote:
> > # up/down scroll button
> > drivers/input/serio/i8042.c: 9c <- i8042 (interrupt, 0, 1) [592682]
> > drivers/input/serio/i8042.c: df <- i8042 (interrupt, 1, 12) [596318]
> > psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
> > drivers/input/serio/i8042.c: 21 <- i8042 (interrupt, 1, 12) [596321]
> > psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
> > drivers/input/serio/i8042.c: 20 <- i8042 (interrupt, 1, 12) [596323]
> > psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1
> > drivers/input/serio/i8042.c: 18 <- i8042 (interrupt, 1, 12) [596325]
> > drivers/input/serio/i8042.c: 67 <- i8042 (interrupt, 1, 12) [596328]
> > drivers/input/serio/i8042.c: 00 <- i8042 (interrupt, 1, 12) [596331]
> 
> Thank you for the debug data. It looks like the scroll buttons on your
> box send 0xdf instead of 0xcf. That should be pretty easy to fix, please
> stay tuned.
> 

Ok, how about this one to begin with?

Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
---
 drivers/input/mouse/alps.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux/drivers/input/mouse/alps.c
===================================================================
--- linux.orig/drivers/input/mouse/alps.c
+++ linux/drivers/input/mouse/alps.c
@@ -54,7 +54,7 @@ static const struct alps_model_info alps
 	{ { 0x20, 0x02, 0x0e },	0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT }, /* XXX */
 	{ { 0x22, 0x02, 0x0a },	0xf8, 0xf8, ALPS_PASS | ALPS_DUALPOINT },
 	{ { 0x22, 0x02, 0x14 }, 0xff, 0xff, ALPS_PASS | ALPS_DUALPOINT }, /* Dell Latitude D600 */
-	{ { 0x73, 0x02, 0x50 }, 0xcf, 0xff, ALPS_FW_BK_1 } /* Dell Vostro 1400 */
+	{ { 0x73, 0x02, 0x50 }, 0xcf, 0xcf, ALPS_FW_BK_1 } /* Dell Vostro 1400 */
 };
 
 /*

-- 
Dmitry

  reply	other threads:[~2008-01-16 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14 20:26 psmouse.c: GlidePoint at isa0060/serio1/input0 lost sync at byte 1 Vegard Nossum
2008-01-07 20:24 ` [BISECTED] " Vegard Nossum
2008-01-11 14:47   ` Dmitry Torokhov
2008-01-15 18:28     ` Vegard Nossum
2008-01-15 20:49       ` Dmitry Torokhov
2008-01-16 15:42         ` Dmitry Torokhov [this message]
2008-01-16 17:46           ` Vegard Nossum
2008-01-16 19:33             ` Dmitry Torokhov
2008-01-16 20:19               ` Vegard Nossum
2008-01-16 20:49                 ` Dmitry Torokhov
2008-01-17 20:26                   ` Vegard Nossum
2008-01-17 21:11                     ` 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=20080116104024.ZZRA012@mailhub.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vegard.nossum@gmail.com \
    --cc=william.pettersson@gmail.com \
    /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).