Re: Synaptics Touchpad workaround for strange behavior after Syncloss (With Patch). (fwd)

From: Gunter Königsmann
Date: Sun Jan 11 2004 - 12:23:26 EST


Last mail from me for this theme:

The kernel version without Your patches gets sync losses even when I use
the i8042.nomux=1 parameter.

Yours,

Gunter.

On Today, Dmitry Torokhov wrote:

>From: Dmitry Torokhov <dtor_core@xxxxxxxxxxxxx>
>Date: Sun, 11 Jan 2004 11:38:49 -0500
>To: Gunter Königsmann <gunter.koenigsmann@xxxxxx>,
> Gunter Königsmann <gunter@xxxxxxxxxxxx>
>Delivered-To: GMX delivery to gunter.koenigsmann@xxxxxx
>Cc: linux-kernel@xxxxxxxxxxxxxxx, Vojtech Pavlik <vojtech@xxxxxxx>,
> Peter Berg Larsen <pebl@xxxxxxxxxx>
>Subject: Re: Synaptics Touchpad workaround for strange behavior after Sync
> loss (With Patch). (fwd)
>
>On Sunday 11 January 2004 11:27 am, Gunter Königsmann wrote:
>> Strike! Helps.
>>
>> No more warnings, no more bad clicks, and a *real* smooth movement.
>>
>
>Great!
>
>Could you tell us what kind of laptop you have (manufacturer/model)
>so other people would not have such pain as you had with it?
>
>> Never thought, a touchpad can work *this* well... ;-)
>>
>> Anyway, I still get those 4 lines on leaving X, but don't know, if it
>> is an error of the kernel, anyway, and doesn't do anything bad exept of
>> warning me:
>>
>> atkbd.c: Unknown key released (translated set 2, code 0x7a on
>> isa0060/serio0). atkbd.c: Unknown key released (translated set 2, code
>> 0x7a on isa0060/serio0). atkbd.c: Unknown key released (translated set
>> 2, code 0x7a on isa0060/serio0). atkbd.c: Unknown key released
>> (translated set 2, code 0x7a on isa0060/serio0).
>
>I believe Vojtech said that it's because X on startup tries to talk to the
>keyboard controller directly, nothing to worry about... But I might be
>mistaken.
>
>>
>>
>> Yours,
>>
>> Gunter.
>
>Dmitry
>
>

--
If today is the first day of the rest of your life, what the hell was yesterday?
---fortune(6)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/