From: Andrew Morton <akpm@linux-foundation.org>
To: federico ferri <xaero@inwind.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] change SysRq keycode for systems without SysRq key
Date: Mon, 16 Jul 2007 23:57:48 -0700 [thread overview]
Message-ID: <20070716235748.33d50a53.akpm@linux-foundation.org> (raw)
In-Reply-To: <4697ECA1.4070200@inwind.it>
On Fri, 13 Jul 2007 23:20:33 +0200 federico ferri <xaero@inwind.it> wrote:
> #ifdef CONFIG_MAGIC_SYSRQ /* Handle the SysRq Hack */
> - if (keycode == KEY_SYSRQ && (sysrq_down || (down == 1 && sysrq_alt))) {
> + if (keycode == CONFIG_MAGIC_SYSRQ_KEYCODE && (sysrq_down || (down == 1 && sysrq_alt))) {
> sysrq_down = down;
> return;
> }
> diff -uprN linux.orig/lib/Kconfig.debug linux/lib/Kconfig.debug
> --- linux.orig/lib/Kconfig.debug 2005-07-09 21:47:22.000000000 +0200
> +++ linux/lib/Kconfig.debug 2005-07-09 21:50:44.000000000 +0200
> @@ -28,6 +28,16 @@ config MAGIC_SYSRQ
> send a BREAK and then within 5 seconds a command keypress. The
> keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
> unless you really know what this hack does.
> +
> +config MAGIC_SYSRQ_KEYCODE
> + int
> + prompt "Change SysRq key-code" if MAGIC_SYSRQ
> + default 99
> + depends on MAGIC_SYSRQ
> + help
> + If your keyboard doesn't have a SysRq key (also labeled PrintScr),
> + you can specify another keycode which should act as SysRq.
> + Default is 99 (KEY_SYSRQ).
> + You can find this number using programs like evtest, or (maybe)
> + showkey.
>
Seems harmless enough ;)
Could you please send in a suitable update to Documentation/sysrq.txt?
next prev parent reply other threads:[~2007-07-17 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 21:20 [PATCH] change SysRq keycode for systems without SysRq key federico ferri
2007-07-17 6:57 ` Andrew Morton [this message]
2007-07-17 22:28 ` federico ferri
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=20070716235748.33d50a53.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xaero@inwind.it \
/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