From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Carlos Corbacho <cathectic@slackadelic.com>
Cc: linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: Enabling "extra" scancodes on some Acer laptops
Date: Tue, 16 Oct 2007 11:52:17 -0400 [thread overview]
Message-ID: <d120d5000710160852x566d6379i96410c2eebabfecf@mail.gmail.com> (raw)
In-Reply-To: <200710161612.40914.cathectic@slackadelic.com>
On 10/16/07, Carlos Corbacho <cathectic@slackadelic.com> wrote:
> Dimitry,
>
> On Tuesday 16 October 2007 15:37:37 you wrote:
> > I think it could be added to i8042 driver to enable it. How messy is
> > detection?
>
> I use simple DMI matching in acer_acpi to do this on known broken laptops.
>
> (acerhk calls directly into the BIOS to find this information - but I suspect
> the data from that could easily be extracted and converted to proper DMI
> table entries).
>
> These are the the three that I know of (and are supported by acer_acpi) that
> require this quirk:
>
> static struct dmi_system_id dritek_extension_quirk[] = {
> {
> .callback = dmi_matched,
> .ident = "Acer Aspire 5650",
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
> DMI_MATCH(DMI_PRODUCT_NAME, "Aspire 5650"),
> },
> },
> {
> .callback = dmi_matched,
> .ident = "Acer Aspire 5680",
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
> DMI_MATCH(DMI_PRODUCT_NAME, "Aspire 5680"),
> },
> },
> {
> .callback = dmi_matched,
> .ident = "Acer TravelMate 2490",
> .matches = {
> DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
> DMI_MATCH(DMI_PRODUCT_NAME, "TravelMate 2490"),
> },
> },
> {}
> };
>
OK, we should be able to add it to i8042 pretty easily.
--
Dmitry
next prev parent reply other threads:[~2007-10-16 15:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 17:03 Enabling "extra" scancodes on some Acer laptops Carlos Corbacho
2007-10-16 14:37 ` Dmitry Torokhov
2007-10-16 15:12 ` Carlos Corbacho
2007-10-16 15:52 ` Dmitry Torokhov [this message]
2007-12-11 18:28 ` Carlos Corbacho
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=d120d5000710160852x566d6379i96410c2eebabfecf@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=cathectic@slackadelic.com \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
/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).