linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: Florian Ragwitz <rafl@debian.org>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: More info on the elantech touchpad
Date: Mon, 10 May 2010 21:34:02 +0100	[thread overview]
Message-ID: <1273523642.2308.651.camel@localhost.localdomain> (raw)
In-Reply-To: <4BE86ABE.5040400@tudelft.nl>

On Mon, 2010-05-10 at 22:21 +0200, Éric Piel wrote:
> Hello,
> 
> There is a version apparently developed for the Dell mini 10 of the
> elantech driver which brings some light on the versions and the protocol.
> 
> It was hidden in some ubuntu git trees [1] (warning, the code hurts the
> eyes):
> http://zinc.ubuntu.com/git?p=mid-team/hardy-netbook.git;a=blob;f=drivers/input/mouse/elantech.c;h=d0e2cafed162428f72e3654f4dda85e08ea486b3;hb=refs/heads/abi-22
> 
> In particular the elantech_init() function is very instructive about the
> various available versions.
> 
> Hopefully someone can merge this code with the current kernel version,
> so we get something that detects automatically most hardware...

Arjen already has the code, as well as some custom Elantech user-space
drivers and code on top of it. But he didn't have any hardware.

I noticed that Peter was working on the Dell mini 10 Elantech touchpad
and passed the code up to him as well.

Cheers

> See you,
> Eric
> 
> [1] kudos to Bastien Nocera for spotting it out:
> http://www.hadess.net/2009/05/dell-mini-10-gah.html


--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2010-05-10 20:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 20:21 More info on the elantech touchpad Éric Piel
2010-05-10 20:34 ` Bastien Nocera [this message]

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=1273523642.2308.651.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=E.A.B.Piel@tudelft.nl \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=rafl@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).