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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20091015195136.GD8544@core.coreip.homeip.net>
Date:	Thu, 15 Oct 2009 12:51:37 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Éric Piel <Eric.Piel@...mplin-utc.net>
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

On Thu, Oct 15, 2009 at 09:32:23PM +0200, Éric Piel wrote:
> 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).

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/