All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linux Input <linux-input@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Jason Wessel <jason.wessel@windriver.com>
Subject: Re: [RFC] Input: implement sysrq as an input handler
Date: Thu, 18 Mar 2010 17:13:35 -0700	[thread overview]
Message-ID: <4BA2C1AF.7010205@oracle.com> (raw)
In-Reply-To: <20100317061952.GA19789@core.coreip.homeip.net>

On 03/16/10 23:19, Dmitry Torokhov wrote:
> Instead of keeping SysRq support inside of legacy keyboard driver split
> it out into a separate input handler (filter). This stops most SysRq input
> events from leaking into evdev clients (some events, such as first SysRq
> scancode - not keycode - event, are still leaked into both legacy keyboard
> and evdev).
> 
> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
> ---
> 
>  drivers/char/keyboard.c |   40 +-------
>  drivers/char/sysrq.c    |  222 +++++++++++++++++++++++++++++++++++++++++------
>  include/linux/sysrq.h   |   23 +----
>  kernel/sysctl.c         |   23 +++++
>  4 files changed, 224 insertions(+), 84 deletions(-)


> +/* Simple translation table for the SysRq keys */
> +static const unsigned char sysrq_xlate[KEY_MAX + 1] =
> +        "\000\0331234567890-=\177\t"                    /* 0x00 - 0x0f */
> +        "qwertyuiop[]\r\000as"                          /* 0x10 - 0x1f */
> +        "dfghjkl;'`\000\\zxcv"                          /* 0x20 - 0x2f */
> +        "bnm,./\000*\000 \000\201\202\203\204\205"      /* 0x30 - 0x3f */
> +        "\206\207\210\211\212\000\000789-456+1"         /* 0x40 - 0x4f */
> +        "230\177\000\000\213\214\000\000\000\000\000\000\000\000\000\000" /* 0x50 - 0x5f */
> +        "\r\000/";                                      /* 0x60 - 0x6f */

We are running out of these precious sysrq keys.
Do you have any ideas of how to have a larger xlate table?

-- 
~Randy

  parent reply	other threads:[~2010-03-19  0:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-17  6:19 [RFC] Input: implement sysrq as an input handler Dmitry Torokhov
2010-03-19  0:00 ` Henrique de Moraes Holschuh
2010-03-19  0:09   ` Dmitry Torokhov
2010-03-19 16:06     ` Henrique de Moraes Holschuh
2010-03-19 18:03       ` Dmitry Torokhov
2010-03-20  2:53         ` Henrique de Moraes Holschuh
2010-03-22  4:59           ` Dmitry Torokhov
2010-04-01 13:34             ` Pavel Machek
2010-04-01 15:42               ` Dmitry Torokhov
2010-04-04 13:27                 ` Pavel Machek
2010-04-16  5:33                   ` Dmitry Torokhov
2010-03-19  0:13 ` Randy Dunlap [this message]
2010-03-19  0:30   ` Dmitry Torokhov

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=4BA2C1AF.7010205@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-input@vger.kernel.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 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.