From: Chuck Ebbert <76306.1226@compuserve.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input <linux-input@atrey.karlin.mff.cuni.cz>
Subject: Re: Magic Alt-SysRq change in 2.6.18-rc1
Date: Sun, 9 Jul 2006 20:01:26 -0400 [thread overview]
Message-ID: <200607092004_MC3-1-C488-137B@compuserve.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0607091657490.28904-100000@netrider.rowland.org>
On Sun, 9 Jul 2006 17:06:57 -0400, Alan Stern wrote:
>
> <...> changes in the behavior of Alt-SysRq?
>
> Before 2.6.18-rc1, I used to be able to use it as follows:
>
> Press and hold an Alt key,
> Press and hold the SysRq key,
> Release the Alt key,
> Press and release some hot key like S or T or 7,
> Repeat the previous step as many times as desired,
> Release the SysRq key.
>
> This scheme doesn't work any more, or if it does, the timing requirements
> are now much stricter. In practice I have to hold down all three keys at
> the same time; I can't release the Alt key before pressing the hot key.
Look at the change history for keyboard.c:
[PATCH] fix magic sysrq on strange keyboards
Magic sysrq fails to work on many keyboards, particulary most of notebook
keyboards. This patch fixes it.
The idea is quite simple: Discard the SysRq break code if Alt is still being
held down. This way the broken keyboard can send the break code (or the user
with a normal keyboard can release the SysRq key) and the kernel waits until
the next key is pressed or the Alt key is released.
--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
next reply other threads:[~2006-07-10 0:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 0:01 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-09 21:06 Magic Alt-SysRq change in 2.6.18-rc1 Alan Stern
2006-07-10 0:22 ` Andrew Morton
2006-07-10 1:12 ` H. Peter Anvin
2006-07-10 3:08 ` Joshua Hudson
2006-07-10 9:44 ` Fredrik Roubert
2006-07-10 9:59 ` Michael Buesch
2006-07-10 21:59 ` Roman Zippel
2006-07-11 12:41 ` Pavel Machek
2006-07-11 22:21 ` Roman Zippel
2006-07-11 12:42 ` Pavel Machek
2006-07-11 13:54 ` Alan Stern
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=200607092004_MC3-1-C488-137B@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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.