From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: acahalan@cs.uml.edu (Albert D. Cahalan),
dwguest@win.tue.nl (Guest section DW),
hpa@zytor.com (H. Peter Anvin),
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Unisys pc keyboard new keys patch, kernel 2.4.3
Date: 16 Apr 2001 23:30:29 -0600 [thread overview]
Message-ID: <m1zodgrt3e.fsf@frodo.biederman.org> (raw)
In-Reply-To: <E14pIo2-0001G8-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Tue, 17 Apr 2001 00:53:15 +0100 (BST)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> > Yes, but they could be. Changing the Linux keycodes is a major
> > break with compatibility. If the Linux keycodes are to be changed,
> > then they ought to be become something that would allow XFree86
> > to become keyboard-independent. Why invent yet another encoding?
>
> You dont need to break compatibility. We have cooked, raw, semi-raw type modes
> for keyboard right now. We just need to add semi-raw-extended and raw-extended
Of course don't have raw via terminal escape string, which can be a royal pain
on a remote machine, if you know how to use the raw keycodes.
Eric
next prev parent reply other threads:[~2001-04-17 5:32 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 [this message]
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
-- 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=m1zodgrt3e.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=acahalan@cs.uml.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dwguest@win.tue.nl \
--cc=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.