linux-kernel - Re: [PATCH 2/2] eeepc-wmi: Add support for T101MT Home/Express Gate key

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110324200958.GC31713@thinkpad-t410>
Date:	Thu, 24 Mar 2011 15:09:58 -0500
From:	Seth Forshee <seth.forshee@...onical.com>
To:	Corentin Chary <corentin.chary@...il.com>
Cc:	Chris Bagwell <chris@...bagwell.com>,
	Matthew Garrett <mjg@...hat.com>,
	acpi4asus-user@...ts.sourceforge.net,
	platform-driver-x86@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] eeepc-wmi: Add support for T101MT Home/Express Gate
 key

On Thu, Mar 24, 2011 at 03:03:55PM -0500, Seth Forshee wrote:
> @@ -79,6 +94,52 @@ static const struct key_entry eeepc_wmi_keymap[] = {
>  	{ KE_END, 0},
>  };
>  
> +static void eeepc_wmi_key_filter(struct asus_wmi_driver *asus_wmi, int *code,
> +				 int *value, int *autorelease)
> +{
> +	struct eeepc_wmi_driver *eeepc = to_eeepc_wmi_driver(asus_wmi);
> +	int is_press;
> +
> +	/*
> +	 * The following behavior is used for T101MT "Home" key:
> +	 * 
> +	 *   On press:   No event set
> +	 *   On hold:    KEY_PROG2 press sent once w/o autorelease
> +	 *   On release: If key was held, KEY_PROG2 release sent.
> +	 *               Otherwise KEY_HOME press sent w/ autorelease.

Doh, just noticed that this comment is incorrect. I'll fix it, but I'll
wait for comments before sending new patches.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/