From: Carlos Corbacho <carlos@strangeworlds.co.uk>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Enabling "extra" scancodes on some Acer laptops
Date: Tue, 11 Dec 2007 18:28:29 +0000 [thread overview]
Message-ID: <200712111828.30142.carlos@strangeworlds.co.uk> (raw)
In-Reply-To: <d120d5000710160852x566d6379i96410c2eebabfecf@mail.gmail.com>
On Tuesday 16 October 2007 16:52:17 Dmitry Torokhov wrote:
> > 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"),
> > },
> > },
> > [etc...]
> > };
>
> OK, we should be able to add it to i8042 pretty easily.
Ok, I completely forgot about this thread...
Dmitry - where would be the best place to add this? Put the DMI matching in
i8042-x86ia64io.h, and then run the quirk somewhere in i8042.c?
-Carlos
--
E-Mail: carlos@strangeworlds.co.uk
Web: strangeworlds.co.uk
GPG Key ID: 0x23EE722D
prev parent reply other threads:[~2007-12-11 18:30 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
2007-12-11 18:28 ` Carlos Corbacho [this message]
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=200712111828.30142.carlos@strangeworlds.co.uk \
--to=carlos@strangeworlds.co.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.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).