From: "Richard Schütz" <r.schtz@t-online.de>
To: Nestor Lopez Casado <nlopezcasad@logitech.com>
Cc: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Jiri Kosina <jkosina@suse.cz>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
rtitmuss@logitech.com, ogay@logitech.com, jzanone@logitech.com
Subject: Re: [PATCH v5 1/1] HID: Add full support for Logitech Unifying receivers
Date: Thu, 29 Sep 2011 17:22:17 +0200 [thread overview]
Message-ID: <4E848D29.4050405@t-online.de> (raw)
In-Reply-To: <CAN+gG=EaHAW504Bi7PDtdsCT0pfs0=BAW5Pt+pSKkkyS5DXfhw@mail.gmail.com>
Am 23.09.2011 00:21, schrieb Benjamin Tissoires:
> On Thu, Sep 22, 2011 at 23:17, Richard Schütz<r.schtz@t-online.de> wrote:
>> Am 22.09.2011 22:48, schrieb Benjamin Tissoires:
>>>
>>> Hi Richard,
>>>
>>> here, you'll find a small C program that allows you to do a pairing of
>>> a new device to a receiver.
>>
>> Thanks.
>>
>> Could you also add the possibility to remove a pairing? It would be nice if
>> the program would print the product name of device detected during the
>> pairing process, too.
>
> mmm... this would be more complicated:
> - the first problem is a NDA and political one. As I worked in
> Logitech, I had access to some internal (confidential) documentation.
> I was able to release this piece of code as it can be easily retrieved
> by adding a spy on the usb stack when doing the pairing on windows.
> Discovering the command that removes devices is not so easy (to my
> mind), thus, I can not give it right now. Please note that I asked
> them if I could release this magic sequence, and it went quite high in
> the hierarchy (but this piece of code has nothing to do with Logitech,
> just to be clear).
> - the second problem is more a technical one. The removal of the
> device would require you two know which device you want to remove. So
> it would require the ability to know all the different devices and
> their pairing number. This information shows up somewhere in the log
> but there is no way to ask the receiver for this information with the
> current status of the driver (without knowing internal commands).
> Getting it from the list of devices would be quite complicated
> depending on the number of receivers you have plugged, etc...
> - Obtaining the name of the device can not be retrieved at the moment
> without knowing the different commands to send to the device. As it's
> confidential Logitech, I can not give them to you unless someone else
> does the retro-engineering.
>
> So, to sum up, I agree this would be better, but today, this has to be
> done by someone else, either officially at Logitech, or by someone not
> related to Logitech that does the retro-engineering.
So what do the Logitech guys think about this? Without userspace tools
for creating/removing pairings a Unifying receiver is quite useless for
Linux users.
--
Regards,
Richard Schütz
--
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:[~2011-09-29 15:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 16:48 [PATCH v5 1/1] HID: Add full support for Logitech Unifying receivers Nestor Lopez Casado
2011-09-15 9:36 ` Jiri Kosina
2011-09-19 20:12 ` Richard Schütz
2011-09-22 20:48 ` Benjamin Tissoires
2011-09-22 21:17 ` Richard Schütz
2011-09-22 22:21 ` Benjamin Tissoires
2011-09-29 15:22 ` Richard Schütz [this message]
2012-04-17 8:28 ` Jiri Kosina
2012-04-17 16:50 ` simon
2012-04-23 11:07 ` Benjamin Tissoires
2012-04-23 13:45 ` Jiri Kosina
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=4E848D29.4050405@t-online.de \
--to=r.schtz@t-online.de \
--cc=benjamin.tissoires@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=jzanone@logitech.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nlopezcasad@logitech.com \
--cc=ogay@logitech.com \
--cc=rtitmuss@logitech.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 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).