Re: Lenovo 3000 N100 i8042 problems

[Jiri Kosina]

On Tue, 2 Sep 2008, Dmitry Torokhov wrote:

> I guess we could use System's product name to differentiate between 
> Cristopher's and Daniel's boards. Although I must admit it is the very 
> first time when I see a box that behaves better with active mux. DOes 
> Vista use active mux nowadays? Because if it is not then I bet there is 
> (or shortly will be) a BIOS update fixing legacy mode on Daniel's box.

I guess so, yes.

On the other hand, this might also be viewed as regression (we made 
Daniel's hardware behave worse with recent kernel than it did before), so 
I think we still would like to have this fixed. What about the patch 
below, adding the match on System's product name, as you suggested? 
Thanks.


From: Jiri Kosina <jkosina@xxxxxxx>
Subject: [PATCH] Input: i8042 - make Lenovo 3000 N100 blacklist entry more specific

Apparently, there are more different versions of Lenovo 3000 N100, some
of them working properly with active mux, and some of them requiring it
being switched off.

This patch applies 'nomux' only to the specific product name that is
reported to behave badly unless 'nomux' is specified.

Signed-off-by: Jiri Kosina <jkosina@xxxxxxx>
---
 drivers/input/serio/i8042-x86ia64io.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/input/serio/i8042-x86ia64io.h b/drivers/input/serio/i8042-x86ia64io.h
index 3282b74..5aafe24 100644
--- a/drivers/input/serio/i8042-x86ia64io.h
+++ b/drivers/input/serio/i8042-x86ia64io.h
@@ -305,7 +305,7 @@ static struct dmi_system_id __initdata i8042_dmi_nomux_table[] = {
 		.ident = "Lenovo 3000 n100",
 		.matches = {
 			DMI_MATCH(DMI_SYS_VENDOR, "LENOVO"),
-			DMI_MATCH(DMI_PRODUCT_VERSION, "3000 N100"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "076804U"),
 		},
 	},
 	{
-- 
1.5.4.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/