From: Santiago Garcia Mantinan <manty@manty.net>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Lukas Hejtmanek <xhejtman@mail.muni.cz>,
Michal Jaegermann <michal@harddata.com>,
linux-kernel@vger.kernel.org
Subject: Re: Synaptics PS/2 driver and 2.6.0-test11
Date: Mon, 8 Dec 2003 12:22:17 +0100 [thread overview]
Message-ID: <20031208112216.GA925@man.beta.es> (raw)
In-Reply-To: <200312071954.31897.dtor_core@ameritech.net>
> The difference is that GPM (I assume you are using it to get Synaptics
Well, as for me I don't have GPM around for anything, I have this setup in
X both for 2.4 and 2.6:
Option "Device" "/dev/psaux"
Option "Protocol" "auto-dev"
> support) only logs "protocol violations" when in debug mode, and then it
> only checks 2 first bytes. The XFree driver does check the protocol but
> its messages usually don't show up in the syslog. In other words in-kernel
> Synaptics driver just makes the problem apparent it seems.
I had thought something like that some time ago, that I had the problem in
both 2.4 and 2.6, but I only had it reported in 2.6. But testing them I
realised that the behaviour of the mouse is totally different, in 2.6 it
goes mad, while in 2.4 it works perfectly, completely smooth, so I dropped
that idea.
The main difference for my setup of the 2.4 and 2.6 kernels relating mouse
is that on 2.6 I have the Synaptics driver in the kernel and also that in
2.4 I don't have INPUT_* and in 2.6 I have INPUT_MOUSEDEV and INPUT_EVDEV.
I don't know the internals of the drivers here, but I can test whatever you
want, do you think that trying to set this up in 2.6 without Synaptics
support will help us know what is going on? any other test? If so I'll try
them!
If you think about some other tests I can make... just tell me.
Regards...
--
Manty/BestiaTester -> http://manty.net
next prev parent reply other threads:[~2003-12-08 11:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 21:46 Synaptics PS/2 driver and 2.6.0-test11 Lukas Hejtmanek
2003-11-30 22:28 ` Dmitry Torokhov
2003-11-30 22:39 ` Lukas Hejtmanek
2003-11-30 23:26 ` Dmitry Torokhov
2003-11-30 23:40 ` Lukas Hejtmanek
2003-12-01 3:25 ` Michal Jaegermann
2003-12-06 12:37 ` Kjartan Maraas
2003-12-07 19:44 ` Lukas Hejtmanek
2003-12-07 22:10 ` Santiago Garcia Mantinan
2003-12-08 0:54 ` Dmitry Torokhov
2003-12-08 9:54 ` Peter Berg Larsen
2003-12-08 18:16 ` Dmitry Torokhov
2003-12-14 23:10 ` Lukas Hejtmanek
2003-12-08 11:22 ` Santiago Garcia Mantinan [this message]
[not found] ` <20031130230144.GA2124@rivenstone.net>
2003-11-30 23:11 ` Lukas Hejtmanek
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=20031208112216.GA925@man.beta.es \
--to=manty@manty.net \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@harddata.com \
--cc=xhejtman@mail.muni.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;
as well as URLs for NNTP newsgroup(s).