linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dumitru Ciobarcianu <Dumitru.Ciobarcianu@iNES.RO>
To: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1-ac2 issues / Toshiba Laptop keyboard
Date: 17 Jul 2003 23:40:21 +0300	[thread overview]
Message-ID: <1058474421.1724.3.camel@LNX.iNES.RO> (raw)
In-Reply-To: <20030717201039.GC25759@charite.de>

[-- Attachment #1: Type: text/plain, Size: 599 bytes --]

On Thu, 2003-07-17 at 23:10, Ralf Hildebrandt wrote:
> * James H. Cloos Jr. <cloos@jhcloos.com>:
> > Ralf> atkbd.c: Unknown key (set 2, scancode 0xa2, on isa0060/serio0) pressed.
> > Ralf> atkbd.c: Unknown key (set 2, scancode 0x92, on isa0060/serio0) pressed.

> But this happened while typing NORMALLY, with no frills :) I mean, I
> was just typing in some unix commands - so I never even came close to
> the keys I never use anyway...


I noticed the same oddity on my Toshiba Sattelite Pro 6100 and choosed
to silece it with the following (trivial) patch. No side effects so
far..




-- 
Cioby

[-- Attachment #2: atkbd-silent.patch --]
[-- Type: text/plain, Size: 647 bytes --]

--- linux-2.5.74/drivers/input/keyboard/atkbd.c.original	2003-07-06 12:08:45.122831824 +0300
+++ linux-2.5.74/drivers/input/keyboard/atkbd.c	2003-07-06 12:09:41.183309336 +0300
@@ -191,8 +191,8 @@
 		case ATKBD_KEY_NULL:
 			break;
 		case ATKBD_KEY_UNKNOWN:
-			printk(KERN_WARNING "atkbd.c: Unknown key (set %d, scancode %#x, on %s) %s.\n",
-				atkbd->set, code, serio->phys, atkbd->release ? "released" : "pressed");
+/*			printk(KERN_WARNING "atkbd.c: Unknown key (set %d, scancode %#x, on %s) %s.\n", 
+				atkbd->set, code, serio->phys, atkbd->release ? "released" : "pressed"); */
 			break;
 		default:
 			input_regs(&atkbd->dev, regs);

  reply	other threads:[~2003-07-17 20:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 14:18 Ralf Hildebrandt
2003-07-17 14:33 ` Michael Kristensen
2003-07-17 14:36   ` Ralf Hildebrandt
2003-07-17 14:38 ` Alan Cox
2003-07-17 14:45   ` Ralf Hildebrandt
2003-07-17 18:24     ` Alvaro Lopes
2003-07-17 20:09       ` Ralf Hildebrandt
2003-07-17 18:15 ` James H. Cloos Jr.
2003-07-17 20:10   ` Ralf Hildebrandt
2003-07-17 20:40     ` Dumitru Ciobarcianu [this message]
2003-07-18  6:36       ` Ralf Hildebrandt
2003-07-18 12:45         ` Alvaro Lopes
2003-07-18 13:49           ` Ralf Hildebrandt
2003-07-17 21:18     ` James H. Cloos Jr.
2003-07-18  6:44       ` Ralf Hildebrandt
2003-07-19 13:18         ` Chris Heath
2003-07-17 20:55 Grover, Andrew
2003-07-18 12:43 ` Alvaro Lopes

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=1058474421.1724.3.camel@LNX.iNES.RO \
    --to=dumitru.ciobarcianu@ines.ro \
    --cc=Ralf.Hildebrandt@charite.de \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: 2.6.0-test1-ac2 issues / Toshiba Laptop keyboard' \
    /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

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).