mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: "Gunter Königsmann" <gunter.koenigsmann@gmx.de>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>,
	linux-kernel@vger.kernel.org, Peter Berg Larsen <pebl@math.ku.dk>
Subject: Re: Synaptics Touchpad workaround for strange behavior after Sync loss (With Patch). (fwd)
Date: Sun, 11 Jan 2004 19:08:07 +0100	[thread overview]
Message-ID: <20040111180807.GB30920@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.53.0401111652510.1271@calcula.uni-erlangen.de>

On Sun, Jan 11, 2004 at 05:27:16PM +0100, Gunter Königsmann wrote:

> Strike! Helps.
> 
> No more warnings, no more bad clicks, and a *real* smooth movement.
> 
> 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).

It's an XFree86 error. It's accessing the keyboard controller directly
behind the kernel's back. It even could cause the controller to fall out
of MUX mode.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR

      parent reply	other threads:[~2004-01-11 18:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-11 16:27 Gunter Königsmann
2004-01-11 16:38 ` Dmitry Torokhov
2004-01-11 17:13   ` Gunter Königsmann
2004-01-11 17:23   ` Gunter Königsmann
2004-02-04  9:27   ` Gunter Königsmann
2004-01-11 18:08 ` Vojtech Pavlik [this message]

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=20040111180807.GB30920@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dtor_core@ameritech.net \
    --cc=gunter.koenigsmann@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebl@math.ku.dk \
    /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

all inboxes | Powered by JetHome®