All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Peter Osterlund <petero2@telia.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Zilvinas Valinskas <zilvinas@gemtek.lt>,
	alistair@devzero.co.uk, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: 2.6.0-test5-mm4
Date: Mon, 22 Sep 2003 23:45:26 +0200	[thread overview]
Message-ID: <20030922214526.GD2983@ucw.cz> (raw)
In-Reply-To: <m2oexc345m.fsf@p4.localdomain>

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 ...

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

WARNING: multiple messages have this Message-ID (diff)
From: Vojtech Pavlik <vojtech@suse.cz>
To: Peter Osterlund <petero2@telia.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Zilvinas Valinskas <zilvinas@gemtek.lt>,
	alistair@devzero.co.uk, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: 2.6.0-test5-mm4
Date: Mon, 22 Sep 2003 23:45:26 +0200	[thread overview]
Message-ID: <20030922214526.GD2983@ucw.cz> (raw)
In-Reply-To: <m2oexc345m.fsf@p4.localdomain>

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 ...

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
--
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>

  reply	other threads:[~2003-09-22 21:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22  8:35 2.6.0-test5-mm4 Andrew Morton
2003-09-22  8:35 ` 2.6.0-test5-mm4 Andrew Morton
2003-09-22 11:49 ` 2.6.0-test5-mm4: BeFS compile error Adrian Bunk
2003-09-22 17:57   ` Will Dyson
2003-09-22 12:09 ` 2.6.0-test5-mm4 Florian Schanda
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 12:17   ` 2.6.0-test5-mm4 Alistair J Strachan
2003-09-22 13:48   ` 2.6.0-test5-mm4 viro
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: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:30     ` 2.6.0-test5-mm4 Florian Schanda
2003-09-22 14:36   ` 2.6.0-test5-mm4 Zilvinas Valinskas
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: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 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 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:27         ` 2.6.0-test5-mm4 Peter Osterlund
2003-09-22 21:45         ` Vojtech Pavlik [this message]
2003-09-22 21:45           ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-25  0:13           ` 2.6.0-test5-mm4 Peter Osterlund
2003-09-25  0:13             ` 2.6.0-test5-mm4 Peter Osterlund
2003-09-25 12:43             ` 2.6.0-test5-mm4 Vojtech Pavlik
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-22 21:44         ` 2.6.0-test5-mm4 Vojtech Pavlik
2003-09-22 19:10 ` 2.6.0-test5-mm4: wanxl doesn't compile with gcc 2.95 Adrian Bunk
2003-09-22 19:22   ` Andrew Morton
2003-09-22 22:42   ` Krzysztof Halasa
2003-09-22 22:41     ` Andrew Morton
2003-09-23 13:24       ` Krzysztof Halasa
2003-09-24  9:18 ` 2.6.0-test5-mm4 boot crash Helge Hafting
2003-09-24  9:18   ` Helge Hafting
2003-09-24  9:57   ` viro
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=20030922214526.GD2983@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=akpm@osdl.org \
    --cc=alistair@devzero.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=petero2@telia.com \
    --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 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.