Thread (22 messages) 22 messages, 2 authors, 2009-10-25

Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore

From: Éric Piel <Eric.Piel@tremplin-utc.net>
Date: 2009-10-15 19:33:20
Also in: lkml

Op 15-10-09 20:13, Dmitry Torokhov schreef:
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).
sftp://piel@localhost:2226/home/piel/busy/i8042-begin-boot-keyboard.dmesg
BTW, do you have i8042.reset parameyer on your command line? What
happens if you remove it?
The two logs where done with i8042.reset. However, without this 
parameter, the behaviour is identical: the keyboard needs the 
unbind/bind trick after the first resume.

Eric

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help