All of lore.kernel.org
 help / color / mirror / Atom feed
From: legolas558 <legolas558@email.it>
To: linux-input@vger.kernel.org
Cc: Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [PATCH] Make Dell keyboard repeat quirk apply to a wider range of hardware
Date: Thu, 14 Aug 2008 06:50:30 +0200	[thread overview]
Message-ID: <48A3B996.3080409@email.it> (raw)
In-Reply-To: <20080814033255.GA21721@srcf.ucam.org>

Hello there.

In this kernel bug http://bugzilla.kernel.org/show_bug.cgi?id=9147 we 
are experiencing a problem with Fn keys when ACPI is active.
Maybe this patch will fix bug 9147 as side-effect?

Thank you,
--
  Daniele C.

Matthew Garrett ha scritto:
> Dell laptops fail to send key up events for several of their special 
> keys. There's an existing quirk in the kernel to handle this, but it's 
> limited to the Latitude range. This patch extends it to cover all 
> portable Dells.
>
> Signed-off-by: Matthew Garrett <mjg@redhat.com>
>
> ---
> diff --git a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
> index b1ce10f..e32c24d 100644
> --- a/drivers/input/keyboard/atkbd.c
> +++ b/drivers/input/keyboard/atkbd.c
> @@ -834,10 +834,10 @@ static void atkbd_disconnect(struct serio *serio)
>  }
>  
>  /*
> - * Most special keys (Fn+F?) on Dell Latitudes do not generate release
> + * Most special keys (Fn+F?) on Dell laptops do not generate release
>   * events so we have to do it ourselves.
>   */
> -static void atkbd_latitude_keymap_fixup(struct atkbd *atkbd)
> +static void atkbd_dell_laptop_keymap_fixup(struct atkbd *atkbd)
>  {
>  	const unsigned int forced_release_keys[] = {
>  		0x85, 0x86, 0x87, 0x88, 0x89, 0x8a, 0x8b, 0x8f, 0x93,
> @@ -1461,13 +1461,13 @@ static int __init atkbd_setup_fixup(const struct dmi_system_id *id)
>  
>  static struct dmi_system_id atkbd_dmi_quirk_table[] __initdata = {
>  	{
> -		.ident = "Dell Latitude series",
> +		.ident = "Dell Laptop",
>  		.matches = {
>  			DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> -			DMI_MATCH(DMI_PRODUCT_NAME, "Latitude"),
> +			DMI_MATCH(DMI_CHASSIS_TYPE, "8"), /* Portable */
>  		},
>  		.callback = atkbd_setup_fixup,
> -		.driver_data = atkbd_latitude_keymap_fixup,
> +		.driver_data = atkbd_dell_laptop_keymap_fixup,
>  	},
>  	{
>  		.ident = "HP 2133",
>
>   


  reply	other threads:[~2008-08-14  5:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14  3:32 [PATCH] Make Dell keyboard repeat quirk apply to a wider range of hardware Matthew Garrett
2008-08-14  4:50 ` legolas558 [this message]
2008-08-14 11:15   ` Matthew Garrett
2008-08-15 19:04 ` Dmitry Torokhov
  -- strict thread matches above, loose matches on Subject: below --
2008-11-11  7:47 Nick Warne
2008-11-12 13:14 ` Nick Warne
2008-11-12 16:45   ` Andreas Mohr
2008-11-12 16:56   ` Matthew Garrett
2008-11-12 17:24     ` Nick Warne
2008-11-12 17:27       ` Matthew Garrett
2008-11-12 17:40         ` Nick Warne
2008-11-12 17:41           ` Matthew Garrett
2008-11-15 12:32     ` Nick Warne
2008-12-29 11:36     ` 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=48A3B996.3080409@email.it \
    --to=legolas558@email.it \
    --cc=linux-input@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.