All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
	Carla Rosenfield <c.rosenfield@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>
Subject: Re: ASUS N550JK Touchpad recognized wrongly as PS/2 mouse
Date: Mon, 20 Oct 2014 19:56:39 +0200	[thread overview]
Message-ID: <54454CD7.80406@redhat.com> (raw)
In-Reply-To: <CAN+gG=E6c9eK51RxMQU_1tkxk08WtXfpSt7eyiz4fZqOd258OQ@mail.gmail.com>

Hi,

On 10/20/2014 05:38 PM, Benjamin Tissoires wrote:
> Hi Carla,
> 
> just FYI, I have the same laptop model than you, and can reproduce
> your bug report in the same way. I'll work on that to make it working
> properly.
> 
> Hans, (unfortunately,) this laptop has a ETD0105 touchpad from Elan.
> That means that we do not have the X550 touchpad in house, but also
> means that we should be able to get in working faster than the X550
> one :)

Ok, so 2 things:

1) On the ETD0105 touchpad not working, does the kernel you're using
already have this patch ? :

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/input/mouse/elantech.c?id=271329b3c798b2102120f5df829071c211ef00ed

If not, try that, if it does, it may need some tweaks to that patch,
or something similar.

2) On not having an X550 style touchpad, I got a report from a user
in the bugzilla tracking that, telling us that he is busy reverse
engineering the protocol, and is making good progress, so that one
should hopefully get sorted out soon-ish too :)

Regards,

Hans

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-08  2:52 ASUS N550JK Touchpad recognized wrongly as PS/2 mouse Carla Rosenfield
2014-10-20 15:38 ` Benjamin Tissoires
2014-10-20 17:56   ` Hans de Goede [this message]
2014-10-20 19:48     ` Benjamin Tissoires
2014-10-21  6:26       ` Hans de Goede
2014-10-23 17:49         ` Benjamin Tissoires

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=54454CD7.80406@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=benjamin.tissoires@gmail.com \
    --cc=c.rosenfield@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 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.