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 15:49:23 -0500	[thread overview]
Message-ID: <20080116154524.ZZRA012@mailhub.coreip.homeip.net> (raw)
In-Reply-To: <19f34abd0801161219oe478b50se13c0710759d581f@mail.gmail.com>

On Wed, Jan 16, 2008 at 09:19:23PM +0100, Vegard Nossum wrote:
> On Jan 16, 2008 8:33 PM, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> > On Wed, Jan 16, 2008 at 06:46:46PM +0100, Vegard Nossum wrote:
> > >
> > > I have now tried this patch. I don't see a sync error now, but the
> > > button still does not work as expected. Now the scroll down button
> > > acts like a middle button instead of scrolling down.
> > >
> > > I am sorry for the confusion; on my laptop it looks like a single
> > > button, but in fact it can be pressed in four different ways (up,
> > > down, left, and right). In 2.6.23, pressing left or right, I get the
> > > traditional paste functionality. Pressing up or down, it acts like a
> > > scroll wheel (up or down). In 2.6.24-rc1, it is the scrolling up/down
> > > that causes the lost sync (but the left/right works correctly).
> > >
> >
> > I see. Could you please provide me with another debug log of all
> > 4 presses/releases of all the buttons, with the patch applied?
> > Do it in the following order please: left, right, middle, up, down.
> 
> Ok. Remember, there really is no dedicated middle button (I've been
> using left button for this purpose, i.e. pasting in X). Here's the
> log. I cannot tell why the first keypress is twice the size of the
> rest, maybe I accidentally pressed it twice, though I tried not to.
> 

Hmm, it seems to work properly, I think it is now a setup issue to a
certain degree. The touchpad now works in native mode (as opposed to
Intellimouse emulation) and so I'd recommend installing Synaptics X
driver from http://web.telia.com/~u89404340/touchpad/

Just to verify, could you please locate evtest utility and check
whether your up and down buttons generate BTN_FORWARD and BTN_BACK
events?

-- 
Dmitry

  reply	other threads:[~2008-01-16 20:49 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
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 [this message]
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=20080116154524.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).