From: Matthew Garrett <mjg59@srcf.ucam.org>
To: dtor@mail.ru
Cc: Nick Warne <nick@ukfsn.org>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: [PATCH] Input: atkbd - broaden the Dell DMI signatures
Date: Mon, 29 Dec 2008 14:29:02 +0000 [thread overview]
Message-ID: <20081229142902.GC31266@srcf.ucam.org> (raw)
In-Reply-To: <20081229113621.1a64caea@sauron.linicks.net>
Some Dells need the dell input quirk applied but have a different vendor
string in their DMI tables. Add an extra entry to cover these machines as
well.
Signed-off-by: Matthew Garrett <mjg@redhat.com>
---
Dmitry, any chance of getting this queued for .29? Probably suitable for
-stable as well.
diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
index 379b7ff..d48de0c 100644
--- a/drivers/input/keyboard/atkbd.c
+++ b/drivers/input/keyboard/atkbd.c
@@ -1476,6 +1476,15 @@ static struct dmi_system_id atkbd_dmi_quirk_table[] __initdata = {
.driver_data = atkbd_dell_laptop_keymap_fixup,
},
{
+ .ident = "Dell Laptop",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Dell Computer Corporation"),
+ DMI_MATCH(DMI_CHASSIS_TYPE, "8"), /* Portable */
+ },
+ .callback = atkbd_setup_fixup,
+ .driver_data = atkbd_dell_laptop_keymap_fixup,
+ },
+ {
.ident = "HP 2133",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"),
--
Matthew Garrett | mjg59@srcf.ucam.org
next parent reply other threads:[~2008-12-29 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081111074702.75e71055@sauron.linicks.net>
[not found] ` <20081112131427.1bbc2a7c@palantir.linicks.net>
[not found] ` <20081112165650.GA15594@srcf.ucam.org>
[not found] ` <20081229113621.1a64caea@sauron.linicks.net>
2008-12-29 14:29 ` Matthew Garrett [this message]
2008-12-30 4:15 ` [PATCH] Input: atkbd - broaden the Dell DMI signatures Dmitry Torokhov
2009-01-04 17:49 ` Nick Warne
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=20081229142902.GC31266@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=dtor@mail.ru \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@ukfsn.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).