From: Andrzej Pietrasiewicz <andrzej.p@collabora.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Slaby <jirislaby@kernel.org>,
kernel@collabora.com
Subject: Re: [RFC] tty/sysrq: Add alternative SysRq key
Date: Thu, 4 Nov 2021 13:21:44 +0100 [thread overview]
Message-ID: <17ccc35d-441c-70c1-a80a-28a4ff824535@collabora.com> (raw)
In-Reply-To: <20211104120111.GB23122@duo.ucw.cz>
Hi Pavel,
W dniu 04.11.2021 o 13:01, Pavel Machek pisze:
> Hi!
>
>> There exist machines which don't have SysRq key at all, e.g. chromebooks.
>>
>> This patch allows configuring an alternative key to act as SysRq. Devices
>> which declare KEY_SYSRQ in their 'keybit' bitmap continue using KEY_SYSRQ,
>> but other devices use the alternative SysRq key instead, by default F10.
>> Which key is actually used can be modified with sysrq's module
>> parameter.
>
> Is F10 sensible default? Would it make sense to use something like
> alt-shift-esc so that this can be enabled by default?
Why "alt-shift-esc" could be enabled by default? Do you mean to enable it for
all systems regardless of whether they declare or don't declare KEY_SYSRQ
in their 'keybit' bitmap?
Andrzej
next prev parent reply other threads:[~2021-11-04 12:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 15:54 Andrzej Pietrasiewicz
2021-11-03 16:19 ` Randy Dunlap
2021-11-04 8:44 ` Andrzej Pietrasiewicz
2021-11-04 9:34 ` Andrzej Pietrasiewicz
2021-11-04 9:52 ` Greg Kroah-Hartman
2021-11-04 12:01 ` Pavel Machek
2021-11-04 12:21 ` Andrzej Pietrasiewicz [this message]
2021-11-04 13:07 ` Maciej W. Rozycki
2021-11-04 13:13 ` Maciej W. Rozycki
2021-11-04 14:17 ` Andrzej Pietrasiewicz
2021-11-05 13:01 ` Andrzej Pietrasiewicz
2021-11-05 13:27 ` Greg Kroah-Hartman
2021-11-05 14:06 ` Andrzej Pietrasiewicz
2021-11-15 14:48 ` Andrzej Pietrasiewicz
2021-11-15 15:09 ` Greg Kroah-Hartman
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=17ccc35d-441c-70c1-a80a-28a4ff824535@collabora.com \
--to=andrzej.p@collabora.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®