From: Kurt Garloff <garloff@suse.de>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Some strange patch to drivers/input/keybdev.c
Date: Fri, 23 Mar 2001 11:04:13 +0100 [thread overview]
Message-ID: <20010323110413.D12408@garloff.casa-etp.nl> (raw)
In-Reply-To: <20010322214255.A4737@devserv.devel.redhat.com>
In-Reply-To: <20010322214255.A4737@devserv.devel.redhat.com>; from zaitcev@redhat.com on Thu, Mar 22, 2001 at 09:42:55PM -0500
[-- Attachment #1.1: Type: text/plain, Size: 827 bytes --]
Hi,
On Thu, Mar 22, 2001 at 09:42:55PM -0500, Pete Zaitcev wrote:
> Some guy sent me the attached patch. He says it allows
> him to use 2 additional keys on the 106 key USB keyboard.
> I never saw a 106 key keyboard before, USB or not.
> Does anyone understand what is going on? Vojtech?
don't know if it's related, but new keyboards tend to have those annoying
APM keys. On my keyboard, they generate the scan sequences e0 5e (Power
OFF), e0 5f (Sleep) and e0 63 (Wake Up). I guess the USB kbd also has those
toy keys.
Patch to support those keys on a normal PS/2 kbd attached.
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG SCSI, Security
[-- Attachment #1.2: linux2216-apm-keys.diff --]
[-- Type: text/plain, Size: 1312 bytes --]
--- linux.compile.old/drivers/char/pc_keyb.c Tue Jul 11 15:00:25 2000
+++ linux.compile/drivers/char/pc_keyb.c Wed Jan 31 18:51:41 2001
@@ -153,6 +153,10 @@
#define E1_PAUSE 119
+#define E0_PWOFF 115
+#define E0_SLEEP 116
+#define E0_ALARM 117
+
/*
* The keycodes below are randomly located in 89-95,112-118,120-127.
* They could be thrown away (and all occurrences below replaced by 0),
@@ -230,10 +234,10 @@
0, 0, 0, 0, 0, E0_KPSLASH, 0, E0_PRSCR, /* 0x30-0x37 */
E0_RALT, 0, 0, 0, 0, E0_F13, E0_F14, E0_HELP, /* 0x38-0x3f */
E0_DO, E0_F17, 0, 0, 0, 0, E0_BREAK, E0_HOME, /* 0x40-0x47 */
- E0_UP, E0_PGUP, 0, E0_LEFT, E0_OK, E0_RIGHT, E0_KPMINPLUS, E0_END,/* 0x48-0x4f */
+ E0_UP, E0_PGUP, 0, E0_LEFT, E0_OK, E0_RIGHT, E0_KPMINPLUS, E0_END, /* 0x48-0x4f */
E0_DOWN, E0_PGDN, E0_INS, E0_DEL, 0, 0, 0, 0, /* 0x50-0x57 */
- 0, 0, 0, E0_MSLW, E0_MSRW, E0_MSTM, 0, 0, /* 0x58-0x5f */
- 0, 0, 0, 0, 0, 0, 0, 0, /* 0x60-0x67 */
+ 0, 0, 0, E0_MSLW, E0_MSRW, E0_MSTM, E0_PWOFF, E0_SLEEP, /* 0x58-0x5f */
+ 0, 0, 0, E0_ALARM, 0, 0, 0, 0, /* 0x60-0x67 */
0, 0, 0, 0, 0, 0, 0, E0_MACRO, /* 0x68-0x6f */
0, 0, 0, 0, 0, 0, 0, 0, /* 0x70-0x77 */
0, 0, 0, 0, 0, 0, 0, 0 /* 0x78-0x7f */
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-03-23 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-23 2:42 Pete Zaitcev
2001-03-23 10:04 ` Kurt Garloff [this message]
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=20010323110413.D12408@garloff.casa-etp.nl \
--to=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.com \
/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
all inboxes | Powered by JetHome®