From: federico <xaero@inwind.it>
To: linux-kernel@vger.kernel.org
Subject: Re: setkeycodes, sysrq, and USB keyboard
Date: Tue, 05 Jul 2005 11:21:09 +0200 [thread overview]
Message-ID: <42CA5105.60505@inwind.it> (raw)
In-Reply-To: <20050704220532.GA2086@ucw.cz>
Vojtech Pavlik ha scritto:
>Sorry, you can't use 'setkeycodes' on USB keyboards. They don't use the
>PS/2 protocol, and hence it doesn't make sense.
>
>
ouch! cannot push SysRq?!?
do I still need my PS/2 keyboard plugged in?
(that keyboard is terribly useful because it is a USB hub... but having
the need to plug a PS/2 keyboard whenever X locks up is a waste of
forces... and a waste of keyboards)
isn't there a workaround for this??
an option in the kernel .config to hardcode sysrq-scancodes would be
fine. sorry but i never look in the deep of the kernel. if you point me
to some branch of the kernel maybe i could hack it :9
ciao!
--
Federico
next prev parent reply other threads:[~2005-07-05 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 21:43 setkeycodes, sysrq, and USB keyboard federico
2005-07-04 22:05 ` Vojtech Pavlik
2005-07-05 9:21 ` federico [this message]
2005-07-05 15:27 ` setkeycodes (KDSETKEYCODE: Invalid argument) Dominik Karall
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=42CA5105.60505@inwind.it \
--to=xaero@inwind.it \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox