All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Luis Henriques <luis.henriques@canonical.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: i8042 - add mux quirk for HP EliteBook 8470p
Date: Tue, 28 Oct 2014 13:10:46 -0700	[thread overview]
Message-ID: <20141028201046.GB7461@dtor-ws> (raw)
In-Reply-To: <1414525704-8409-1-git-send-email-luis.henriques@canonical.com>

Hi Luis,

On Tue, Oct 28, 2014 at 07:48:24PM +0000, Luis Henriques wrote:
> This laptop requires active multiplexing to be enabled in order to be able
> to separate the PS/2 mouse and the touchpad.
> 
> Signed-off-by: Luis Henriques <luis.henriques@canonical.com>
> ---
>  drivers/input/serio/i8042-x86ia64io.h | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/drivers/input/serio/i8042-x86ia64io.h b/drivers/input/serio/i8042-x86ia64io.h
> index a0bcbb64d06d..34b95e4268eb 100644
> --- a/drivers/input/serio/i8042-x86ia64io.h
> +++ b/drivers/input/serio/i8042-x86ia64io.h
> @@ -220,6 +220,13 @@ static const struct dmi_system_id __initconst i8042_dmi_mux_table[] = {
>  			DMI_MATCH(DMI_PRODUCT_NAME, "CF-18"),
>  		},
>  	},
> +	{
> +		/* HP EliteBook 8470p */
> +		.matches = {
> +			DMI_MATCH(DMI_SYS_VENDOR, "Hewlett-Packard"),
> +			DMI_MATCH(DMI_PRODUCT_NAME, "HP EliteBook 8470p"),

Hmm, so the tide is turning the other way ;) I think I'll be comfortable
extending this to all EliteBooks as I know 840 and 1040 work as well and
I have not heard any other complaints about this model line.

Cold you resend with match on "HP EliteBook" instead of "HP EliteBook
8470p"?

Thanks.

-- 
Dmitry

  reply	other threads:[~2014-10-28 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-28 19:48 [PATCH] Input: i8042 - add mux quirk for HP EliteBook 8470p Luis Henriques
2014-10-28 20:10 ` Dmitry Torokhov [this message]
2014-10-28 22:25   ` Luis Henriques

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=20141028201046.GB7461@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luis.henriques@canonical.com \
    /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.