All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Unisys pc keyboard new keys patch, kernel 2.4.3
Date: 14 Apr 2001 23:29:38 -0700	[thread overview]
Message-ID: <9bbf4i$qs7$1@cesium.transmeta.com> (raw)
In-Reply-To: <20010413150219.A440@napalm.go.cz> <20010414002120.A15596@win.tue.nl> <20010414201250.A7260@napalm.go.cz>

Followup to:  <20010414201250.A7260@napalm.go.cz>
By author:    Jan Dvorak <johnydog@go.cz>
In newsgroup: linux.dev.kernel
>
> On Sat, Apr 14, 2001 at 12:21:20AM +0200, Guest section DW wrote:
> > No, these codes cannot be larger than 127 today.
> > You can use the utility setkeycodes to assign keycodes to these keys.
> I always tought it is 8bit - more-than-128-keys keyboards exists quite long
> time. 
> 

No, the top bit is make/break.

	-hpa
-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

  reply	other threads:[~2001-04-15  6:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-13 13:02 [PATCH] Unisys pc keyboard new keys patch, kernel 2.4.3 Jan Dvorak
2001-04-13 22:21 ` Guest section DW
2001-04-13 23:53   ` H. Peter Anvin
2001-04-16  6:29     ` Eric W. Biederman
2001-04-16 17:41       ` Guest section DW
2001-04-16 19:52         ` Albert D. Cahalan
2001-04-16 23:53           ` Alan Cox
2001-04-17  5:30             ` Eric W. Biederman
2001-04-16  6:54     ` Albert D. Cahalan
2001-04-16  6:59       ` H. Peter Anvin
2001-04-14 18:12   ` Jan Dvorak
2001-04-15  6:29     ` H. Peter Anvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-15 16:40 James Simmons
2001-04-17 16:55 James Simmons
2001-04-17 17:16 ` Alan Cox
2001-04-17 17:51 James Simmons

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='9bbf4i$qs7$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --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.