From: Bernd Schubert <bernd-schubert@web.de>
To: roychris <roychris@free.fr>, Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org, r31@rnbhq.org
Subject: Re: psmouse.c, throwing 3 bytes away
Date: Mon, 9 Feb 2004 23:25:34 +0100 [thread overview]
Message-ID: <200402092325.34895.bernd-schubert@web.de> (raw)
In-Reply-To: <40278077.5070409@free.fr>
On Monday 09 February 2004 13:43, roychris wrote:
> I resolved this problem. It's the fault of the multiplexing on i8042.
> You must pass i8042_nomux=1 to the kernel for 2.4.X or 2.6.0 or you must
> modify
> linux-2.6.x/drivers/input/serio/i8042.c by quoting many lines if > 2.6.0
> because nomux doesn't work :
>
>
> /* if (!i8042_noaux && !i8042_check_aux(&i8042_aux_values)) {
> if (!i8042_nomux && !i8042_check_mux(&i8042_aux_values))
> for (i = 0; i < 4; i++) {
> i8042_init_mux_values(i8042_mux_values +
> i, i804
> 2_mux_port + i, i);
> i8042_port_register(i8042_mux_values +
> i, i8042_
> mux_port + i);
> }
> else
> */
> i8042_port_register(&i8042_aux_values, &i8042_aux_port);
> // }
>
Hello Roychris,
on 2.4.25-rc1 the i8042_nomux=1 option causes the following:
- on a single read on /proc/apm the mouse still jumps
- several/few reads make the mouse to stop and only to work after a few
seconds
- a fast endless read makes the mouse to stop at all and never work again
Commenting out the lines in 2.6.2-rc2 causes the mouse not to work at all. No
error messages, nothing in the logs.
Do you have a Thinkpad R31 and it workes there for you?
Thanks a lot for your help,
Bernd
next prev parent reply other threads:[~2004-02-09 22:25 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 2:20 psmouse.c, throwing 3 bytes away Walt Nelson
2004-02-05 4:54 ` Claudio Martins
2004-02-05 10:20 ` Isaac Claymore
2004-02-09 6:15 ` Isaac Claymore
2004-02-09 9:09 ` Vojtech Pavlik
2004-02-09 9:49 ` Isaac Claymore
2004-02-09 9:52 ` Vojtech Pavlik
2004-02-05 13:40 ` Michael Buesch
2004-02-05 15:31 ` johann lombardi
2004-02-05 5:05 ` Mike Houston
2004-02-05 17:24 ` Murilo Pontes
2004-02-05 20:38 ` Vojtech Pavlik
2004-02-05 18:14 ` Murilo Pontes
2004-02-05 19:08 ` Murilo Pontes
2004-02-05 21:06 ` Michael Buesch
2004-02-05 22:10 ` Mike Houston
2004-02-06 7:15 ` Mike Houston
2004-02-06 8:06 ` Walt Nelson
2004-02-07 5:47 ` Mike Houston
2004-02-07 9:11 ` Murilo Pontes
2004-02-08 21:59 ` Vojtech Pavlik
2004-02-08 22:19 ` aeriksson
2004-02-08 22:32 ` Vojtech Pavlik
2004-02-08 23:03 ` Bernd Schubert
2004-02-08 23:30 ` Vojtech Pavlik
[not found] ` <40278077.5070409@free.fr>
2004-02-09 22:25 ` Bernd Schubert [this message]
2004-02-09 0:48 ` [patch] " Vojtech Pavlik
2004-02-09 1:13 ` Claudio Martins
2004-02-09 1:23 ` Vojtech Pavlik
2004-02-10 2:56 ` Greg Norris
2004-02-10 7:07 ` Vojtech Pavlik
2004-02-10 7:39 ` Walt Nelson
2004-02-10 19:48 ` Greg Norris
2004-02-10 20:08 ` Vojtech Pavlik
2004-02-10 7:33 ` johann lombardi
2004-02-10 21:11 ` Murilo Pontes
2004-02-11 4:44 ` Claudio Martins
2004-02-06 0:33 ` Pete Clements
2004-02-06 22:44 ` Kronos
2004-02-07 2:35 ` Jamie Lokier
2004-02-07 4:19 ` Gene Heskett
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 6:18 Bob Gill
2004-02-05 21:56 Luis Miguel García
2004-02-05 19:33 ` Murilo Pontes
2004-02-06 7:02 ` Claudio Martins
2004-02-06 10:12 ` Christian Unger
2004-02-06 17:52 ` Adrian Bunk
2004-02-06 18:03 ` Michael Buesch
2004-02-06 21:49 ` Claudio Martins
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=200402092325.34895.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=r31@rnbhq.org \
--cc=roychris@free.fr \
--cc=vojtech@suse.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