From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Éric Piel" <Eric.Piel@tremplin-utc.net>
Cc: Greg KH <gregkh@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [REGRESSION] "bind" a device to a driver doesn't not work anymore
Date: Thu, 15 Oct 2009 12:51:37 -0700 [thread overview]
Message-ID: <20091015195136.GD8544@core.coreip.homeip.net> (raw)
In-Reply-To: <4AD778C7.4070707@tremplin-utc.net>
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-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-10-15 19:52 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 2:05 [REGRESSION] "bind" a device to a driver doesn't not work anymore Dmitry Torokhov
2009-10-15 17:24 ` Éric Piel
2009-10-15 18:13 ` Dmitry Torokhov
2009-10-15 18:27 ` Dmitry Torokhov
2009-10-15 19:32 ` Éric Piel
2009-10-15 19:51 ` Dmitry Torokhov [this message]
2009-10-15 21:33 ` Éric Piel
2009-10-15 21:59 ` Dmitry Torokhov
2009-10-15 22:44 ` Éric Piel
2009-10-21 19:34 ` Éric Piel
2009-10-21 20:20 ` Dmitry Torokhov
2009-10-22 16:10 ` Éric Piel
2009-10-22 16:22 ` Dmitry Torokhov
2009-10-22 17:48 ` Éric Piel
2009-10-22 18:19 ` Dmitry Torokhov
2009-10-22 18:32 ` Dmitry Torokhov
2009-10-23 8:08 ` Éric Piel
2009-10-23 8:58 ` Dmitry Torokhov
2009-10-23 9:21 ` Éric Piel
2009-10-23 16:31 ` Dmitry Torokhov
2009-10-25 11:47 ` Éric Piel
2009-10-25 19:07 ` Dmitry Torokhov
-- strict thread matches above, loose matches on Subject: below --
2009-10-11 0:04 Éric Piel
2009-10-11 3:00 ` Greg KH
2009-10-12 4:35 ` Dmitry Torokhov
2009-10-12 11:46 ` Éric Piel
2009-10-12 14:44 ` Greg KH
2009-10-12 15:45 ` Dmitry Torokhov
2009-10-12 17:37 ` Greg KH
2009-10-12 15:48 ` Dmitry Torokhov
2009-10-12 16:48 ` Éric Piel
2009-10-12 17:35 ` Greg KH
2009-10-12 18:33 ` Dmitry Torokhov
2009-10-12 18:54 ` Greg KH
2009-10-12 19:20 ` Dmitry Torokhov
2009-10-12 19:58 ` Greg KH
2009-10-13 3:17 ` Dmitry Torokhov
2009-10-18 7:51 ` Dmitry Torokhov
2009-10-18 8:02 ` Greg KH
2009-10-23 2:01 ` Dmitry Torokhov
2009-10-26 20:59 ` Greg KH
2009-10-26 21:34 ` Dmitry Torokhov
2009-10-26 23:59 ` Greg KH
2009-10-27 16:16 ` Dmitry Torokhov
2009-10-13 9:52 ` Éric Piel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091015195136.GD8544@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Eric.Piel@tremplin-utc.net \
--cc=gregkh@suse.de \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).