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

["Éric Piel" <eric.piel@tremplin-utc.net>]

Op 12-10-09 17:48, Dmitry Torokhov schreef:
> On Mon, Oct 12, 2009 at 01:46:17PM +0200, Éric Piel wrote:
>>> Eric, do you still need to fiddle with i8042 to get your keyboard working with 
>>> 2.6.32-rc3? We need to make sure that resube works without users needing to 
>>> mess with bind/unbind.
>> Yes, the keyboard doesn't work after the first resume from ram (the
>> later resumes do work). I haven't tried any special option to the i8042
>> driver. This is on a HP 2510, in 64 bits.
> 
> Could you please try and let me know if unloading at suspend and
> reloading after resume atkbd and/or psmouse drivers and leaving i8042
> alone "fixes" the issue?
> 
I've just tried adding i8042.reset to the boot command line, and it
doesn't help (still no keyboard after resume). That's actually a bit
surprising because I saw on some forum that in general it helped for the
HP laptops. Is there a way to be sure the command was understood by the
driver? I see nothing confirming in dmesg.

My atkbd and psmouse drivers were built-in, so I'm currently recompiling
the kernel with them as module and will let you know tomorrow.

See you,
Eric
--
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