From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: Florian Ragwitz <rafl@debian.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [PATCH 1/2] elantech: Report tool width when it is known
Date: Wed, 5 May 2010 10:13:50 -0700 [thread overview]
Message-ID: <20100505171350.GE7337@core.coreip.homeip.net> (raw)
In-Reply-To: <4BE1A3AA.1090401@tudelft.nl>
On Wed, May 05, 2010 at 06:58:18PM +0200, Éric Piel wrote:
> Op 05-05-10 18:39, Dmitry Torokhov schreef:
> > On Wed, May 05, 2010 at 02:14:25PM +0200, Éric Piel wrote:
> >> >From observation of the values sent from the hardware version 2, it
> >> seems that the first four bits of byte 1 represents the width. So we can
> >> report it as well. Observed values on my hardware were always between 1
> >> and 12, so let's use this for min and max.
> >>
> >
> > I think we shoudl have threshold for the firmware version when we start
> > reporting the width.
> >
> What do you mean? That the width might not be reported correctly by all
> the firmwares? I have no idea if that is the case. For info, IIRC my
> firmware report 2.1 with middle byte 8.
>
My understanding was that older firmwares would report 0. I might be
mistaken.
--
Dmitry
--
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
next prev parent reply other threads:[~2010-05-05 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 12:14 [PATCH 1/2] elantech: Report tool width when it is known Éric Piel
2010-05-05 16:39 ` Dmitry Torokhov
2010-05-05 16:58 ` Éric Piel
2010-05-05 17:13 ` Dmitry Torokhov [this message]
2010-05-05 18:00 ` Florian Ragwitz
2010-05-05 18:09 ` Dmitry Torokhov
2010-05-05 18:13 ` Éric Piel
2010-05-05 16:53 ` Florian Ragwitz
2010-05-05 17:12 ` Dmitry Torokhov
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=20100505171350.GE7337@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=E.A.B.Piel@tudelft.nl \
--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).