Hi, another piece in the Sixaxis jigsaw: in commit d4bfa033ed84e0ae446eff445d107ffd5ee78df3 support for setting different report types was added to hidp, however in my Sixaxis experiments setting leds (sending and output report) was not working until I made this change: diff --git a/net/bluetooth/hidp/core.c b/net/bluetooth/hidp/core.c index b68a608..0c443b7 100644 --- a/net/bluetooth/hidp/core.c +++ b/net/bluetooth/hidp/core.c @@ -402,7 +402,7 @@ static int hidp_output_raw_report(struct hid_device *hid, unsigned char *data, s report_type = HIDP_TRANS_SET_REPORT | HIDP_DATA_RTYPE_FEATURE; break; case HID_OUTPUT_REPORT: - report_type = HIDP_TRANS_DATA | HIDP_DATA_RTYPE_OUPUT; + report_type = HIDP_TRANS_SET_REPORT | HIDP_DATA_RTYPE_OUPUT; break; default: return -EINVAL; Is it only the Sixaxis which needs the output report as a SET_REPORT operation, or the change above is an actual fix? I don't know bluetooth at all, sorry. In case this is a sixaxis specific behavior then I guess I'll be overriding hidp_output_raw_report() in hid-sony.c just like I did for the usbhid counterpart. Thanks, Antonio -- Antonio Ospite http://ao2.it PGP public key ID: 0x4553B001 A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Attachment:
pgpEUFP3yDEPp.pgp
Description: PGP signature
