From: Vojtech Pavlik <vojtech@suse.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/8] Set of input (psmouse) patches
Date: Wed, 29 Sep 2004 09:11:23 +0200 [thread overview]
Message-ID: <20040929071123.GA2648@ucw.cz> (raw)
In-Reply-To: <200409290140.53350.dtor_core@ameritech.net>
On Wed, Sep 29, 2004 at 01:40:53AM -0500, Dmitry Torokhov wrote:
> Hi Vojtech,
>
> Here is new bunch of small psmouse patches. Nothing particularly interesting
> except probably exporting rate, resolution, resetafter and smartscroll
> parameters as sysfs attributes. Protocol exporting and switching is still
> in progress though...
>
> 01-alps-signature.patch
> - add a new signature to ALPS response table (Inspiron 8500)
>
> 02-rate-resolution-handlers.patch
> - add set_rate and set_resolution handlers to psmouse structure
> to reduce dependencies between protocols, helps wihen exporting
> resolutin and rate via sysfs
>
> 03-synaptics-guest-protocol-switch.patch
> - not only set 4 byte guest protocol but also reset it back to 3
> if for some odd reason user reconnects guest requesting lower
> protocol.
>
> 04-psmouse-probe-fix.patch
> - patch from Marko Macek dealing with probing and his KVM (the thing
> doctors stream and gets confused by the extended probes)
>
> 05-psmouse-sysfs-attr.patch
> - export rate, resolution, resetafter and smartscroll as sysfs
> attributes.
>
> 06-psmouse-drop-ps2tpp.patch
> - get rid of PS2T++ protocol symbol as it it handled exactly the same
> as PS2++. This leaves space for THINKPS protocol and allows keeping
> old Synaptics and Alps protocol numbers that Synaptics X driver
> relied on.
>
> 07-separate-ps2pp-handling.patch
> - complete separation of PS2++ protocol deconding by moving everything
> into logips2pp.c - cleanup.
>
> 08-psmouse-packet-size.patch
> - add pktsize to psmouse structure and check it instead on relying on
> protcol numbering. Also rearrange detect routines in preparation to
> dynamic protocol switching via sysfs.
>
> Please let me know what you think and I will push it on bkbits.
All look OK, except for the last one. I'll comment in the patch itself.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2004-09-29 7:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 6:40 [PATCH 0/8] Set of input (psmouse) patches Dmitry Torokhov
2004-09-29 6:41 ` [PATCH 1/8] New ALPS signature Dmitry Torokhov
2004-09-29 6:42 ` [PATCH 2/8] Psmouse rate and resolution handlers Dmitry Torokhov
2004-09-29 6:43 ` [PATCH 3/8] Guest protocol switch in synaptics Dmitry Torokhov
2004-09-29 6:44 ` [PATCH 4/8] Psmouse probe fixes Dmitry Torokhov
2004-09-29 6:44 ` [PATCH 5/8] Export psmouse parameters via sysfs Dmitry Torokhov
2004-09-29 6:45 ` [PATCH 6/8] Drop PS2TPP protocol identifier Dmitry Torokhov
2004-09-29 6:46 ` [PATCH 7/8] Separate PS2PP protocol handling Dmitry Torokhov
2004-09-29 6:47 ` [PATCH 7/8] Psmouse - add packet size Dmitry Torokhov
2004-09-29 7:15 ` Vojtech Pavlik
2004-09-29 7:29 ` Dmitry Torokhov
2004-09-29 9:31 ` Vojtech Pavlik
2004-09-29 13:24 ` Dmitry Torokhov
2004-09-29 13:38 ` Vojtech Pavlik
2004-09-30 6:43 ` Dmitry Torokhov
2004-09-30 7:55 ` Vojtech Pavlik
2004-09-30 10:34 ` Jan-Benedict Glaw
2004-09-29 7:11 ` Vojtech Pavlik [this message]
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=20040929071123.GA2648@ucw.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.