Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2009-10-15 19:52:31
Also in:
lkml
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2009-10-15 19:52:31
Also in:
lkml
On Thu, Oct 15, 2009 at 09:32:23PM +0200, Éric Piel wrote:
Op 15-10-09 20:13, Dmitry Torokhov schreef:quoted
It lokks like the keyboard controller switched from translated to non-translated mode: '1c' is make code and 'f0 1c' is break (aka release) code. Could you tell me how the keyboard indentified (in dmesg) after fresh boot and after you do the bind/unbind trick on the older kernel?What do you mean by "how the keyboard indentified"? Are you asking for the debug trace in dmesg? I have the beginning of a boot with the debug trace to see after a fresh boot. I don't have dmesg history with i8042.debug of the bind/unbind trick, so I'll reboot in an old kernel and do it again (but I cannot do this before tuesday, when i have physical access to the machine).
No, not the debug.. Just the lines looking like this: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 You should have at leat 2 - one uping initial boot and one after rebinding i8042 upon resume. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html