From: Paul Nasrat <pauln@truemesh.com>
To: Milan Roubal <roubm9am@barbora.ms.mff.cuni.cz>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0test3mm2 - Synaptics touchpad problem
Date: Fri, 15 Aug 2003 12:39:41 +0100 [thread overview]
Message-ID: <20030815113940.GR13037@shitake.truemesh.com> (raw)
In-Reply-To: <00a501c3631c$676237b0$401a71c3@izidor>
On Fri, Aug 15, 2003 at 01:00:09PM +0200, Milan Roubal wrote:
> Hi,
> I am using the new drivers for XFree86 and if the touchpad is visible
Apologies I misread your bug report. Maybe this will be of more help.
> in dmesg, than it is working in XFree86 too. When it isn't,
> it isn't than listed in /proc/bus/input/devices and is not working in
> XFree86.
That does seem odd, I haven't noticed this with vanilla 2.6.0test3
(linux only, but a reboot linux->linux would exhibit that).
I note on the non synaptics boot you have this instead of the synaptics.
serio: i8042 AUX3 port at 0x60,0x64 irq 12
It may be worth #define DEBUG in i8042.c, to see the differences between
the two boot sequences in more detail.
You might want to try against 2.6.0-test3, if it works for you
then it might be worth going through the synaptics patches in mm2 one by
one :(
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.0-test3/2.6.0-test3-mm2/broken-out/
http://w1.894.telia.com/~u89404340/patches/touchpad/2.6.0-test2/v1/Readme.txt
I'll see if I can replicate this with my laptop this evening.
Paul
next prev parent reply other threads:[~2003-08-15 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 9:25 2.6.0test3mm2 - Synaptics touchpad problem Milan Roubal
2003-08-15 10:35 ` Paul Nasrat
2003-08-15 11:00 ` Milan Roubal
2003-08-15 11:39 ` Paul Nasrat [this message]
2003-08-15 12:18 ` Milan Roubal
2003-08-15 13:28 ` Milan Roubal
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=20030815113940.GR13037@shitake.truemesh.com \
--to=pauln@truemesh.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roubm9am@barbora.ms.mff.cuni.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).