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:23:07 +0300 [thread overview]
Message-ID: <0888e980-5511-af8f-bd00-e94916cb6356@kapsi.fi> (raw)
In-Reply-To: <20160725130547.6c9b80c23fef6dfe50ad9979@ao2.it>
On 07/25/16 14:05, Antonio Ospite wrote:
> On Mon, 25 Jul 2016 11:14:04 +0200
> Benjamin Tissoires <benjamin.tissoires@redhat.com> wrote:
>
>> On Jul 21 2016 or thereabouts, Antonio Ospite wrote:
> [...]
>>> It would be interesting to understand why some (supposedly) compatible
>>> devices break, maybe they rely on the fact that the PS3 would use the
>>> original report?
>>
>> [just speculating]
>> I would be *really* surprised if the Sony software were to overwrite the
>> report descriptor of their own sony controllers. My guess is that their
>> HID stack or their Playstation driver is compatible with the original
>> report descriptors and so they can handle the differences between
>> original and weirdo controllers.
>>
>
> That's basically what I was thinking too, in my last sentence I meant
> to write report _descriptor_ :)
>
> Mikko, if you have some time, could you post the original report
> descriptor for your device?
Sure, here's the output from hidrd-convert:
0x05, 0x01, /* Usage Page (Desktop), */
0x09, 0x04, /* Usage (Joystick), */
0xA1, 0x01, /* Collection (Application), */
0x09, 0x01, /* Usage (Pointer), */
0xA1, 0x00, /* Collection (Physical), */
0x05, 0x09, /* Usage Page (Button), */
0x19, 0x01, /* Usage Minimum (01h), */
0x29, 0x0A, /* Usage Maximum (0Ah), */
0x15, 0x00, /* Logical Minimum (0), */
0x25, 0x01, /* Logical Maximum (1), */
0x75, 0x01, /* Report Size (1), */
0x95, 0x0A, /* Report Count (10), */
0x81, 0x02, /* Input (Variable), */
0x95, 0x06, /* Report Count (6), */
0x81, 0x03, /* Input (Constant, Variable), */
0xC0, /* End Collection, */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x15, 0x00, /* Logical Minimum (0), */
0x25, 0x01, /* Logical Maximum (1), */
0x25, 0x01, /* Logical Maximum (1), */
0x25, 0x01, /* Logical Maximum (1), */
0xC0 /* End Collection */
>
> $ hexdump /sys/bus/hid/devices/XXXX\:YYYY\:ZZZZ.0001/report_descriptor
>
> or
>
> $ hidrd-convert -i natv -o code /sys/bus/hid/devices/XXXX\:YYYY\:ZZZZ.0001/report_descriptor
>
> 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
> 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.
next prev parent reply other threads:[~2016-07-25 15:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-17 17:25 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 [this message]
2016-07-25 15:25 ` Mikko Perttunen
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=0888e980-5511-af8f-bd00-e94916cb6356@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
all inboxes | Powered by JetHome®