From mboxrd@z Thu Jan 1 00:00:00 1970 From: federico ferri Subject: Re: [PATCH] input: change SysRq keycode for systems without SysRq key Date: Tue, 17 Jul 2007 08:40:59 +0200 Message-ID: <469C647B.1000307@inwind.it> References: <469A5385.6030402@inwind.it> <469A68CC.5040902@inwind.it> <469A99ED.3090603@inwind.it> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Dmitry Torokhov Cc: Linus Torvalds , linux-input@atrey.karlin.mff.cuni.cz, trivial@kernel.org List-Id: linux-input@vger.kernel.org Dmitry Torokhov ha scritto: >> Dmitry? Any reason not to do this? >> > > Recent kernels have the ability to remap keymap for USB keyboards via > EVIOCSKEYCODE ioctl (we allowed 0adjusting keymaps on PS/2 keyboards > for a long time). So instead of having the new parameter redefining > SysRq keycode Frederico can remap one of the keys on his keyboard to > generate KEY_SYSRQ. This way SysRq should still work if he plugs in > another USB keyboard that has SysRq key or a PS/2 keyboard. would setkeycodes still just work for PS2 keyboards? I upgraded to newer kbd-1.13 package (kernel 2.6.21), and while trying to change sysrq keycode still I get the old error: KDSETKEYCODE: No such device failed to set scancode 38b7 to keycode 84 which I reported on gentoo a long time ago: http://bugs.gentoo.org/show_bug.cgi?id=97388 (it doesn't use EVIOCSKEYCODE) maybe I'm not picking up the right program? -- Federico Ferri