public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries.Brouwer@cwi.nl
To: Andries.Brouwer@cwi.nl, garloff@suse.de
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
	mantel@suse.de, rubini@vision.unipv.it, torvalds@transmeta.com
Subject: Re: [PATCH] make psaux reconnect adjustable
Date: Tue, 14 Aug 2001 11:12:29 GMT	[thread overview]
Message-ID: <200108141112.LAA99888@vlet.cwi.nl> (raw)

    From garloff@garloff.de Tue Aug 14 11:57:23 2001

    I can confirm what you suggest:
	My mouse (Logitech wheel USB/PS2) sends indeed AA 00.
    So, I extended my patch:
    psmouse_reconnect = 0: Do nothing (just pass all to userspace)
    psmouse_reconnect = 1: Flush Q & ping mouse on AA 00 (default)
    psmouse_reconnect = 2: Flush Q & ping mouse on AA (old behaviour)

    With reconnect 1 or 2: After reconnecting, mouse behaves strange
	(jumping around the screen)
    With reconnect 0:      Mouse is dead

    In both cases restarting gpm gets the mouse back to work again.
    It seems the imps2 driver does some initialization to the mouse.

    If I use the plain ps2 driver, then finally, I see the benefit of the
    reconnect code in the kernel:
    With reconnect = 1 or 2: It works after replugging
    With reconnect = 0:      Mouse is dead after replugging

    In the latter case restarting gpm helps.

Before having an opinion about what would be appropriate,
let me make sure that I understand the facts that you report.

You talk about reconnect, but what is your definition of reconnect?
Is it that the mouse sends AA or AA 00, or is it that you unplug
and replug the mouse?

Andries

             reply	other threads:[~2001-08-14 11:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14 11:12 Andries.Brouwer [this message]
2001-08-14 17:10 ` [PATCH] make psaux reconnect adjustable Gunther Mayer
2001-08-14 21:56   ` Kurt Garloff
  -- strict thread matches above, loose matches on Subject: below --
2001-08-14 21:26 Andries.Brouwer
2001-08-14 18:29 Andries.Brouwer
2001-08-14 19:35 ` Gunther Mayer
     [not found] <no.id>
2001-08-02 15:03 ` Alan Cox
2001-08-02 17:34 ` Alan Cox
2001-08-02 17:27 Andries.Brouwer
2001-08-14  9:57 ` Kurt Garloff
2001-08-14 15:03   ` Kurt Garloff
2001-08-14 16:58     ` Linus Torvalds
2001-08-14 17:35       ` Kurt Garloff
2001-08-14 21:29       ` Kurt Garloff
2001-08-15 15:50         ` Gunther Mayer
2001-08-02 16:02 Andries.Brouwer
2001-08-02 16:18 ` Kurt Garloff
2001-08-02 11:55 Andries.Brouwer
2001-08-02  2:21 Kurt Garloff

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=200108141112.LAA99888@vlet.cwi.nl \
    --to=andries.brouwer@cwi.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mantel@suse.de \
    --cc=rubini@vision.unipv.it \
    --cc=torvalds@transmeta.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