All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1-ac2 issues / Toshiba Laptop keyboard
Date: Thu, 17 Jul 2003 22:10:39 +0200	[thread overview]
Message-ID: <20030717201039.GC25759@charite.de> (raw)
In-Reply-To: <m38yqxf2ab.fsf@lugabout.jhcloos.org>

* James H. Cloos Jr. <cloos@jhcloos.com>:

> Ralf> atkbd.c: Unknown key (set 2, scancode 0xb2, on isa0060/serio0) pressed.
> Ralf> atkbd.c: Unknown key (set 2, scancode 0xae, on isa0060/serio0) pressed.
> Ralf> atkbd.c: Unknown key (set 2, scancode 0xb1, on isa0060/serio0) pressed.
> Ralf> atkbd.c: Unknown key (set 2, scancode 0x97, on isa0060/serio0) pressed.
> 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.
> 
> I've been hacking through a similar issue on some Dell laptops.
> 
> You need to add entries to the atkbd_set2_keycode[] array in
> drivers/input/keyboard/atkbd.h.  Look at the #defines in
> inlucde/linux/input.h for stuff that matches the keys that
> five the unknown key printk()s, and put those values in the
> Nth entry of the array, where N is the scancode reported in
> the printk().  
> 
> Eg, if the first key mentioned above were a VolumeUp key, you
> would want to add the value 115 to the 0xb2'th entry in the
> array.

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

-- 
Ralf Hildebrandt (Im Auftrag des Referat V a)   Ralf.Hildebrandt@charite.de
Charite Campus Mitte                            Tel.  +49 (0)30-450 570-155
Referat V a - Kommunikationsnetze -             Fax.  +49 (0)30-450 570-916
AIM: ralfpostfix

  reply	other threads:[~2003-07-17 19:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-17 14:18 2.6.0-test1-ac2 issues / Toshiba Laptop keyboard 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 [this message]
2003-07-17 20:40     ` Dumitru Ciobarcianu
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
  -- strict thread matches above, loose matches on Subject: below --
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=20030717201039.GC25759@charite.de \
    --to=ralf.hildebrandt@charite.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.