public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Tomas Szepe <szepe@pinerecords.com>
Cc: Andrew Morton <akpm@osdl.org>, GCS <gcs@lsc.hu>,
	linux-kernel@vger.kernel.org, Peter Osterlund <petero2@telia.com>
Subject: Re: Synaptics problems in -mm1
Date: Sat, 27 Dec 2003 12:28:58 -0500	[thread overview]
Message-ID: <200312271228.59192.dtor_core@ameritech.net> (raw)
In-Reply-To: <20031227113848.GA10491@louise.pinerecords.com>

On Saturday 27 December 2003 06:38 am, Tomas Szepe wrote:
> Hi,
>
> it seems one of the synaptics-related patches in 2.6.0-mm1 kills
> off the pointer stick on my T40p.  2.6.0 vanilla works just fine
> in that department.  Thought you might want to know.
>
> Reverting
>
> 	input-08-synaptics-protocol-discovery.patch
> 	input-07-remove-synaptics-config-option.patch
> 	synaptics-powerpro-fix.patch
>
> did not seem to help.  I failed to figure out a way to easily revert
>
> 	serio-06-synaptics-use-reconnect.patch
> 	serio-04-synaptics-cleanup.patch
>
> so that I didn't try.

I have a couple of questions (I am not familiar with IBM hardware so
please bear with me...):
- Is it detected as Synaptics but does not work?
- Should it be detected as Synaptics?
- Does it work if you pass psmouse_noext=1 or psmouse_proto=bare?
  And what about psmouse_proto=imps and psmouse_proto=exps
- Does it work if you give 2.6.0-test10-mm1 a quick boot?
- dmesg, input section of you XFree and version and parameters that
  are passed to GPM.

Thank you,

Dmitry

  parent reply	other threads:[~2003-12-27 17:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24  9:59 2.6.0-mm1 GCS
2003-12-24 11:32 ` 2.6.0-mm1 Andrew Morton
2003-12-24 11:53   ` 2.6.0-mm1 GCS
2003-12-24 12:23     ` 2.6.0-mm1 GCS
2003-12-24 15:17       ` 2.6.0-mm1 Dmitry Torokhov
2003-12-24 19:12         ` 2.6.0-mm1 GCS
2003-12-24 12:47   ` 2.6.0-mm1 Thomas Molina
2003-12-25  9:11   ` 2.6.0-mm1 Dmitry Torokhov
2003-12-25  9:13     ` 2.6.0-mm1 - Patch 1/2 - mousedev-remove-jitter Dmitry Torokhov
2003-12-25  9:14       ` 2.6.0-mm1 - Patch 2/2 - mousedev-dont-stop Dmitry Torokhov
2003-12-27 11:38         ` Synaptics problems in -mm1 Tomas Szepe
2003-12-27 12:24           ` GCS
2003-12-27 13:22             ` Tomas Szepe
2003-12-27 17:28           ` Dmitry Torokhov [this message]
2003-12-27 18:11             ` Tomas Szepe
2003-12-27 18:23               ` Dmitry Torokhov
2003-12-27 18:37                 ` Tomas Szepe
2003-12-27 18:45                   ` Dmitry Torokhov
2003-12-27 19:01                     ` Tomas Szepe
2003-12-27 21:00                       ` Dmitry Torokhov
2003-12-28  0:00                   ` Andrew Morton
2003-12-28  0:45                     ` Dmitry Torokhov
2003-12-28  1:21                     ` Tomas Szepe
2003-12-27 17:56           ` Marcos D. Marado Torres
2003-12-27 20:59             ` Dmitry Torokhov
2003-12-25 18:22     ` 2.6.0-mm1 GCS
2003-12-24 14:38 ` 2.6.0-mm1 GCS

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=200312271228.59192.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=gcs@lsc.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.com \
    --cc=szepe@pinerecords.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