From: 정태영 <master@mytears.org>
To: linux-kernel@vger.kernel.org
Subject: In 2.6 kernel, there are 2 problems with Korean keyboard.
Date: Fri, 26 Sep 2003 17:54:33 +0900 [thread overview]
Message-ID: <3F73FEC9.7090109@mytears.org> (raw)
Hi,
In Korean 106-key keyboard, there are two keys aren't working.
Those are, Korean/English Key, and Korean/Chinese Key.
These have scancode of 0xf2, and 0xf1 accordingly, also in xev, it were
recognised as 122 and 121.
In 2.4.xx kernel, these keys send the event correctly, however in
2.6.0_test5, it seems it has problem with sending key events.
It leaves following lines in the kernel log;
Sep 24 03:33:59 [kernel] atkbd.c: Unknown key (set 2, scancode 0xf1, on isa0060/serio0) pressed.
Sep 24 03:33:59 [kernel] atkbd.c: Unknown key (set 2, scancode 0xf2, on isa0060/serio0) pressed.
So I have tried to hack atkbd.c and assigned values to 0xf2 and 0xf1, now the kernel log seems fine but still, xev doesn't receive anything.
Also, while I was searching internet, I have found a patch for an old keyboard driver.
http://www.geocrawler.com/archives/3/2142/2002/2/0/7967619/
How would i be able to use these keys correctly in Kernel 2.6?
Regards
reply other threads:[~2003-09-26 8:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F73FEC9.7090109@mytears.org \
--to=master@mytears.org \
--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