linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikko Perttunen <mikko.perttunen@kapsi.fi>
To: Antonio Ospite <ao2@ao2.it>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: jikos@kernel.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Mikko Perttunen <mperttunen@nvidia.com>
Subject: Re: [PATCH] HID: sony: disable descriptor fixup for FutureMax Dance Mat
Date: Mon, 25 Jul 2016 18:25:03 +0300	[thread overview]
Message-ID: <cd3e71a8-055b-3aa3-076e-cf96b9835232@kapsi.fi> (raw)
In-Reply-To: <0888e980-5511-af8f-bd00-e94916cb6356@kapsi.fi>

On 07/25/16 18:23, Mikko Perttunen wrote:
> On 07/25/16 14:05, Antonio Ospite wrote:
>> You can also find out the length of the raw output report with trial and
>> error, start with a line like this:
>>
>> $ sudo hexdump -v -e '49/1 "%02x " "\n"' /dev/hidraw0
>>
>> and increase/decrease the value (49 works with original controllers)
>> until you see a regular pattern when comparing lines.
>>
>
> /dev/hidraw0 seems to be all zeroes straight from the beginning

Actually, pressing some buttons on the pad, it seems that the report 
length is two bytes

>
>> Anyways this is just for curiosity, we are not going to spend too much
>> time on that... or are we? :)
>
> At least it's some reference information.. :)
>
>>
>> Thanks,
>>    Antonio
>>
>
> Cheers,
> Mikko.
>


      reply	other threads:[~2016-07-25 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-17 17:25 [PATCH] HID: sony: disable descriptor fixup for FutureMax Dance Mat Mikko Perttunen
2016-07-18 14:28 ` Benjamin Tissoires
2016-07-19  6:08   ` Mikko Perttunen
2016-07-21 16:34     ` Antonio Ospite
2016-07-25  9:14       ` Benjamin Tissoires
2016-07-25 11:05         ` Antonio Ospite
2016-07-25 15:23           ` Mikko Perttunen
2016-07-25 15:25             ` Mikko Perttunen [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=cd3e71a8-055b-3aa3-076e-cf96b9835232@kapsi.fi \
    --to=mikko.perttunen@kapsi.fi \
    --cc=ao2@ao2.it \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mperttunen@nvidia.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).