linux-kernel - [PATCH] Make wistron-btns recognize special keys on Medion WIM2160 notebooks

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-next>] [day] [month] [year] [list]

Message-Id: <200709141337.36398.bero@arklinux.org>
Date:	Fri, 14 Sep 2007 13:37:36 +0200
From:	Bernhard Rosenkraenzer <bero@...linux.org>
To:	linux-kernel@...r.kernel.org
Subject: [PATCH] Make wistron-btns recognize special keys on Medion WIM2160 notebooks

The patch below adds support for Medion WIM2160 notebooks to the wistron-btns 
driver.

Signed-off-by: Bernhard Rosenkraenzer <bero@...linux.org>

--- linux-2.6.22/drivers/input/misc/wistron_btns.c.ark	2007-09-07 
22:47:49.000000000 +0000
+++ linux-2.6.22/drivers/input/misc/wistron_btns.c	2007-09-07 
22:54:19.000000000 +0000
@@ -536,6 +536,13 @@
 	{ KE_END, FE_MAIL_LED | FE_WIFI_LED | FE_UNTESTED }
 };
 
+static struct key_entry keymap_medion_wim2160[] __initdata = {
+	{ KE_WIFI, 0x30 },
+	{ KE_KEY, 0x11, {KEY_PROG1} },
+	{ KE_KEY, 0x12, {KEY_PROG2} },
+	{ KE_END, 0 }
+};
+
 static struct key_entry keymap_wistron_md2900[] __initdata = {
 	{ KE_KEY, 0x01, {KEY_HELP} },
 	{ KE_KEY, 0x02, {KEY_CONFIG} },
@@ -917,6 +924,15 @@
 		},
 		.driver_data = keymap_fs_amilo_d88x0
 	},
+	{
+		.callback = dmi_matched,
+		.ident = "Medion WIM2160",
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "MEDION"),
+			DMI_MATCH(DMI_PRODUCT_NAME, "WIM2160"),
+		},
+		.driver_data = keymap_medion_wim2160
+	},
 	{ NULL, }
 };
 
-
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/