From: "Ivo van Doorn" <ivd@linuxmail.org>
To: linux-kernel@vger.kernel.org
Subject: [BUG] setkeycodes with 2.6.0-test5 / -test6
Date: Tue, 30 Sep 2003 10:53:08 +0100 [thread overview]
Message-ID: <20030930095308.19043.qmail@linuxmail.org> (raw)
Hi!
I'va been working on a kernelpatch for the 2.6 test kernel named the Funkey patch. This patch has been created by Rick van Rein for 2.2 and 2.4 kernels: website is here: http://rck.vanrein.org/linux/funkey.
When i ported this patch to 2.6 I run into small problem., which also occurs when no patch is applied.
First I will give a small explanation on how the Funkey patch works:
Modern keyboards have extra multimedia keys (think of the "www" "mail" "search" sound volume etc.) By using setkeycodes to give these buttons a keycode and in the keymap giving that keycode a highbyte the key gets picked up by the funkey patch and instead of sending the signal through /dev/console, it gets send through /dev/funkey. Using the matching daemon the /dev/funkey can be read and programs can be launched when the buton is pressed. "www" button can for example start lynx, or mozilla or whatever.
The problem in ran into was exactly at the beginning of the entire proces: Mapping the keys.
I tried several keys to test the patch on a 2.6.0-test5 and a 2.6.0-test6 kernel.
First key I tried was my "www" key.
showkey -s output was:
0xe0 0x32 0xe0 0xb2
showkey -k output was:
keycode 0 press
keycode 1 release
keycode 22 release
keycode 0 release
keycode 1 release
keycode 22 release
The showkey -k output was unchanged after I ran the command
setkeycodes e032 89
When testing if the setkeycodes command was correct I used it on a 2.4.20 kernel as well. This time it worked.
I repeated the same test with the window buttons between the "alt" and "Control"
showkey -k output was always:
keycode 125 pressed
keycode 125 released
setkeycodes e05b 89
did not help. keycode for this key remained 125.
Before everybody starts shouting my patch is mostl likely the problem:
These results were with an unpatched version of the kernel...
Off course nothing changed when I applied my patch.
Personally I guess this means a small bug in the setkeycodes of the kernel, unless I am doing everything wrong?
Ivo
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
next reply other threads:[~2003-09-30 9:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 9:53 Ivo van Doorn [this message]
2003-09-30 15:07 ` [BUG] setkeycodes with 2.6.0-test5 / -test6 Andries Brouwer
2003-09-30 16:13 ` Vojtech Pavlik
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=20030930095308.19043.qmail@linuxmail.org \
--to=ivd@linuxmail.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