From: Peter Osterlund <petero2@telia.com>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Andrew Morton <akpm@osdl.org>,
Zilvinas Valinskas <zilvinas@gemtek.lt>,
alistair@devzero.co.uk, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: 2.6.0-test5-mm4
Date: 25 Sep 2003 02:13:04 +0200 [thread overview]
Message-ID: <m2u171ene7.fsf@p4.localdomain> (raw)
In-Reply-To: <20030922214526.GD2983@ucw.cz>
Vojtech Pavlik <vojtech@suse.cz> writes:
> On Mon, Sep 22, 2003 at 11:27:17PM +0200, Peter Osterlund wrote:
> > Andrew Morton <akpm@osdl.org> writes:
> >
> > > Zilvinas Valinskas <zilvinas@gemtek.lt> wrote:
> > > >
> > > > Btw Andrew ,
> > > >
> > > > this change "Synaptics" -> "SynPS/2" - breaks driver synaptic driver
> > > > from http://w1.894.telia.com/~u89404340/touchpad/index.html.
> > > >
> > > >
> > > > -static char *psmouse_protocols[] = { "None", "PS/2", "PS2++", "PS2T++", "GenPS/
> > > > 2", "ImPS/2", "ImExPS/2", "Synaptics"};
> > > > +static char *psmouse_protocols[] = { "None", "PS/2", "PS2++", "PS2T++", "GenPS/2", "ImPS/2", "ImExPS/2", "SynPS/2"};
> > >
> > > You mean it breaks the XFree driver? Is it just a matter of editing
> > > XF86Config to tell it the new protocl name?
> >
> > It breaks the event device auto detection, which works by parsing
> > /proc/bus/input/devices. The protocol name is hard coded so you can't
> > just change the XF86Config file.
> >
> > > Either way, it looks like a change which should be reverted?
> >
> > I think the new protocol name is better, so why not just fix the X
> > driver instead. Here is a fixed version:
> >
> > http://w1.894.telia.com/~u89404340/touchpad/synaptics-0.11.4.tar.bz2
>
> I'd suggest the driver either checks the BUS/VENDOR/DEVICE ids or the
> bitfields for the pad, not the name. Names are unreliable ...
OK, this is now implemented in version 0.11.5, which I just uploaded
to my web site. This version also adds support for the new events
ABS_TOOL_WIDTH, BTN_TOOL_FINGER, BTN_TOOL_DOUBLETAP and
BTN_TOOL_TRIPLETAP.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-09-25 0:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 8:35 2.6.0-test5-mm4 Andrew Morton
2003-09-22 12:09 ` 2.6.0-test5-mm4 Florian Schanda
2003-09-22 12:17 ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 13:48 ` 2.6.0-test5-mm4 viro
2003-09-22 14:29 ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 14:30 ` 2.6.0-test5-mm4 Florian Schanda
2003-09-22 14:36 ` 2.6.0-test5-mm4 Zilvinas Valinskas
2003-09-22 13:49 ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 13:54 ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 18:55 ` 2.6.0-test5-mm4 Andrew Morton
2003-09-22 21:27 ` 2.6.0-test5-mm4 Peter Osterlund
2003-09-22 21:45 ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-25 0:13 ` Peter Osterlund [this message]
2003-09-25 12:43 ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-22 21:44 ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-24 9:18 ` 2.6.0-test5-mm4 boot crash Helge Hafting
2003-09-24 9:57 ` viro
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=m2u171ene7.fsf@p4.localdomain \
--to=petero2@telia.com \
--cc=akpm@osdl.org \
--cc=alistair@devzero.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vojtech@suse.cz \
--cc=zilvinas@gemtek.lt \
/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