public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Input patches
Date: Thu, 11 Mar 2004 02:26:23 -0500	[thread overview]
Message-ID: <200403110226.23897.dtor_core@ameritech.net> (raw)

Hi,

I have some more input patches I'd like you to take look at:

psmouse_cleanup_fix:
	When disconnecting PS/2 mouse we marekd it as PSMOUSE_IGNORE too
	early, before protocol's disconnect handler had a chance to run.
	When mouse is in PSMOUSE_IGNORE state it ignores everything,
	including ACKs, which causes cleanup routine to fail.

synaptics-passthrough-fix:
	If touchpad does not support extended protocols (imps, exps) then
	after probing foor said protocols trackpoint on the pass-though
	port may stop working and full reset is needed to revive it
        (just reset-disable is not enough).

synaptics-restore-taps:
	If Synaptics' absolute mode is disabled (by proto= option) make
	sure that touchpad is in relative mode and gestures (taps) are
	enabled. We need specifically reset the mode byte as even full
	reset does not affect it (except for absolute bit).

The patches depend on other input patches submitted earlier. All patches are
available at:

	bk pull bk://dtor.bkbits.net/input
	http://www.geocities.com/dt_or/input/2_6_4

-- 
Dmitry

             reply	other threads:[~2004-03-11  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-11  7:26 Dmitry Torokhov [this message]
2004-03-11  7:30 ` [PATCH 1/3] Input patches: psmouse cleanup fix Dmitry Torokhov
2004-03-11  7:30   ` [PATCH 2/3] Input patches: synaptics passthrough fix Dmitry Torokhov
2004-03-11  7:31     ` [PATCH 3/3] Input patches: synaptics restore taps 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=200403110226.23897.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /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