public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joost Gevers <joost.gevers@tiscali.nl>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: keyboard scancode problems
Date: Thu, 26 Oct 2006 20:03:56 +0200	[thread overview]
Message-ID: <1161885837.6083.19.camel@venus> (raw)

Hello,

I've a laptop with 2 additional keys for the Euro and Dollar (Acer 
TM8106). 

When I press these keys, I get the following error: 
atkbd.c: Unknown key pressed (translated set 2, code 0xb3 on
isa0060/serio0). 
atkbd.c: Use 'setkeycodes e033 <keycode>' to make it known. 
atkbd.c: Unknown key released (translated set 2, code 0xb3 on
isa0060/serio0). 
atkbd.c: Use 'setkeycodes e033 <keycode>' to make it known. 

When I use setkeycodes to link a keycode to a scancode, as shown below: 

setkeycodes 0xb3 205 

(I think that this is the same as: 
setkeycodes e033 205 
At least it gives identical results) 

To make the key know as Euro key, I do the following: 
loadkeys << "EOF" 
keycode  205 = currency 
EOF 

This results in a the Euro sign on my console with 
setfont lat0-16 -m 8859-15 

Now my question: 
When I do a showkey -s, I expect that when I press the Euro key, which
I 
just linked to 0xb3 will be shown. But the following is the result: 
showkey -s 
kb mode was XLATE 

press any key (program terminates after 10s of last keypress)... 
0x9c 
0xe0 0x25 
0xe0 0xa5 

What is the reason that the scancode which I set differs from what is 
shown by showkey? 

With kind regards 
Joost Gevers 




             reply	other threads:[~2006-10-26 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26 18:03 Joost Gevers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-01  0:37 Keyboard Scancode Problems Udo A. Steinberg
2001-02-01 18:55 ` Pierre Rousselet
2001-02-02  7:11 ` Stefan Frank

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=1161885837.6083.19.camel@venus \
    --to=joost.gevers@tiscali.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox