From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Dmitry Torokhov" Subject: Re: Enabling "extra" scancodes on some Acer laptops Date: Tue, 16 Oct 2007 11:52:17 -0400 Message-ID: References: <200710141803.09039.cathectic@slackadelic.com> <200710161612.40914.cathectic@slackadelic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200710161612.40914.cathectic@slackadelic.com> Content-Disposition: inline Sender: owner-linux-input@atrey.karlin.mff.cuni.cz List-Help: List-Owner: List-Post: List-Unsubscribe: To: Carlos Corbacho Cc: linux-input@atrey.karlin.mff.cuni.cz List-Id: linux-input@vger.kernel.org On 10/16/07, Carlos Corbacho 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