From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Fredrik Roubert <roubert@df.lth.se>
Cc: zippel@linux-m68k.org, akpm@osdl.org, pavel@ucw.cz,
stern@rowland.harvard.edu, dmitry.torokhov@gmail.com,
linux-input@atrey.karlin.mff.cuni.cz,
linux-kernel@vger.kernel.org
Subject: Re: [patch] Re: Magic Alt-SysRq change in 2.6.18-rc1
Date: Wed, 12 Jul 2006 08:12:40 -0700 [thread overview]
Message-ID: <20060712081240.6b3ee023.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060712072628.GB5869@igloo.df.lth.se>
On Wed, 12 Jul 2006 09:26:28 +0200 Fredrik Roubert wrote:
> On Wed 12 Jul 02:16 CEST 2006, Roman Zippel wrote:
>
> > > Nack your nack! The patch in 2.6.18-rc1 makes sysrq work on machines on
> > > which it *did not work at all*. If that makes it harder to type but still
> > > possible to type on other machines, well, we win.
> >
> > Why can't we even _try_ to preserve compatibility? :-(
>
> First, please note that the documented behaviour (You press the key
> combo 'ALT-SysRq-<command key>'.) still works.
>
> The problem at hand is that not all keyboards can handle this many keys
> pressed at once, and that there also are keyboards broken in other ways.
>
> The work-around suggested in the documentation ([Y]ou might have better
> luck with "press Alt", "press SysRq", "release Alt", "press <command
> key>", release everything.) does not work with keyboards that sends the
> make and break codes for SysRq immediately after another, and this was
> the reason for changing the behaviour (for broken keyboards) in
> 2.6.18-rc1. The new behaviour works with every keyboard the people
> involved in this discussion has heard of.
>
> That the documentation wasn't updated with the new work-around key
> combination for broken keyboards was a mistake.
In the past, I've had/used several huge-company black
keyboards that didn't work (recognize) Alt-SysRq-X.
Should they work now? (I don't currently have one.)
It would be very nice if they do.
---
~Randy
next prev parent reply other threads:[~2006-07-12 15:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 21:06 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 22:42 ` [patch] " Pavel Machek
2006-07-11 23:33 ` Roman Zippel
2006-07-11 23:50 ` Andrew Morton
2006-07-12 0:16 ` Roman Zippel
2006-07-12 0:37 ` Andrew Morton
2006-07-12 0:52 ` Roman Zippel
2006-07-12 1:36 ` Andrew Morton
2006-07-12 8:08 ` Pavel Machek
2006-07-12 9:07 ` Roman Zippel
2006-07-12 13:26 ` Paulo Marques
2006-07-12 19:42 ` Paulo Marques
2006-07-12 20:05 ` Dmitry Torokhov
2006-07-12 22:21 ` Paulo Marques
2006-07-12 22:44 ` Pavel Machek
2006-07-13 18:48 ` Dmitry Torokhov
2006-07-12 7:26 ` Fredrik Roubert
2006-07-12 9:09 ` Roman Zippel
2006-07-12 15:12 ` Randy.Dunlap [this message]
2006-07-11 12:42 ` Pavel Machek
2006-07-11 13:54 ` Alan Stern
[not found] <6wOHw-5gl-23@gated-at.bofh.it>
[not found] ` <6x0yX-5An-17@gated-at.bofh.it>
[not found] ` <6xc78-6gi-15@gated-at.bofh.it>
[not found] ` <6xyhf-5Fq-1@gated-at.bofh.it>
[not found] ` <6xyU6-6Hn-63@gated-at.bofh.it>
[not found] ` <6xzdl-75B-13@gated-at.bofh.it>
[not found] ` <6xzZO-8gU-23@gated-at.bofh.it>
[not found] ` <6xA9p-8ti-7@gated-at.bofh.it>
[not found] ` <6xACo-Op-1@gated-at.bofh.it>
[not found] ` <6xAVM-1b9-5@gated-at.bofh.it>
[not found] ` <6xBfh-1yd-29@gated-at.bofh.it>
[not found] ` <6xBRQ-2v4-3@gated-at.bofh.it>
[not found] ` <6xITm-4td-17@gated-at.bofh.it>
[not found] ` <6xMX0-2bX-21@gated-at.bofh.it>
2006-07-12 22:06 ` [patch] " Bodo Eggert
2006-07-12 22:35 ` Paulo Marques
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=20060712081240.6b3ee023.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=roubert@df.lth.se \
--cc=stern@rowland.harvard.edu \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®