From: Rafi Rubin <rafi@seas.upenn.edu>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: jkosina@suse.cz, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
chatty@enac.fr, micki@n-trig.com
Subject: Re: [PATCH 3/4] identify firmware version
Date: Sun, 29 Aug 2010 15:55:45 -0400 [thread overview]
Message-ID: <4C7ABB41.1020708@seas.upenn.edu> (raw)
In-Reply-To: <4C77A92F.8020302@euromail.se>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/27/10 08:01, Henrik Rydberg wrote:
> On 08/26/2010 06:54 AM, Rafi Rubin wrote:
>
>> This adds firmware version polling to the end of probe and reports the
>> version both in the raw form and proccessed to match the formatting used
>> by ntrig in windows.
>>
>> Signed-off-by: Rafi Rubin <rafi@seas.upenn.edu>
>
>
> The version field of the input_id struct is a 16-bit number that can be used to
> code device-specific version information, and is retrievable via EVIOCGID.
> Perhaps one could code the firmware version in there.
>
> Henrik
Thanks, I missed that field and will update my approach accordingly.
I suppose in that case, I should also keep the firmware decoding as a userspace
tool.
Micki, would you care to comment on the decoding? Any misplaced bits, or
additional bits you would like to add mappings for?
Rafi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkx6u0EACgkQwuRiAT9o60+8SwCgrjqd+FNJPSEve/tdM7+C0i4/
0xsAmwVg0YDjz3QFukfPyawrZwdoPD3U
=htK1
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-08-29 20:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 4:54 hid-ntrig documentation and firmware id Rafi Rubin
2010-08-26 4:54 ` [PATCH 1/4] Adding documention Rafi Rubin
2010-08-27 12:06 ` Henrik Rydberg
2010-08-29 19:52 ` Rafi Rubin
2010-08-30 13:25 ` Jiri Kosina
2010-08-26 4:54 ` [PATCH 2/4] a bit of whitespace cleanup Rafi Rubin
2010-08-26 4:54 ` [PATCH 3/4] identify firmware version Rafi Rubin
2010-08-27 12:01 ` Henrik Rydberg
2010-08-29 19:55 ` Rafi Rubin [this message]
2010-08-26 4:54 ` [PATCH 4/4] firmware sysfs node Rafi Rubin
2010-08-27 12:09 ` Henrik Rydberg
2010-08-27 16:34 ` Dmitry Torokhov
2010-08-31 2:06 ` Rafi Rubin
2010-09-01 2:06 ` Dmitry Torokhov
2010-09-01 9:48 ` [PATCH] identify firmware version Rafi Rubin
2010-09-01 10:04 ` Rafi Rubin
2010-09-01 12:27 ` Henrik Rydberg
2010-09-01 20:12 ` Jiri Slaby
2010-09-02 0:12 ` Rafi Rubin
2010-09-02 8:03 ` Jiri Slaby
2010-09-02 18:00 ` Rafi Rubin
2010-09-02 18:11 ` Rafi Rubin
2010-09-06 16:42 ` Rafi Rubin
2010-09-06 19:48 ` Dmitry Torokhov
2010-09-06 21:22 ` Jiri Slaby
2010-09-06 23:32 ` Rafi Rubin
2010-09-06 23:36 ` Dmitry Torokhov
2010-09-07 6:54 ` Jiri Slaby
2010-09-08 9:47 ` Jiri Kosina
2010-09-08 15:42 ` Rafi Rubin
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=4C7ABB41.1020708@seas.upenn.edu \
--to=rafi@seas.upenn.edu \
--cc=chatty@enac.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=micki@n-trig.com \
--cc=rydberg@euromail.se \
/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).