[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AD778C7.4070707@tremplin-utc.net>
Date: Thu, 15 Oct 2009 21:32:23 +0200
From: Éric Piel <Eric.Piel@...mplin-utc.net>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Greg KH <gregkh@...e.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>
Subject: Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore
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@...alhost: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
View attachment "i8042-begin-boot-keyboard.dmesg" of type "text/plain" (80974 bytes)
Powered by blists - more mailing lists