From: Oliver Neukum <oneukum@suse.com>
To: linux-ml@bernd-steinhauser.de, linux-usb@vger.kernel.org
Subject: Re: Force Feedback support not recognized on Granite Devices Simucube
Date: Mon, 17 Jun 2019 12:57:18 +0200 [thread overview]
Message-ID: <1560769038.8567.15.camel@suse.com> (raw)
In-Reply-To: <68cebd85-92ad-8059-a767-a8a4f33c5c9e@bernd-steinhauser.de>
Am Montag, den 17.06.2019, 12:35 +0200 schrieb Bernd Steinhauser:
>
> The device advertises as MCS, Granite Devices SimuCUBE with id 16d0:0d5a, I'll attach lsusb output.
> Upon connection, the device is recognized and the output is:
>
> [ 3271.812807] usb 1-2.4.2: new full-speed USB device number 10 using xhci_hcd
> [ 3271.921182] usb 1-2.4.2: New USB device found, idVendor=16d0, idProduct=0d5a, bcdDevice= 2.00
> [ 3271.921184] usb 1-2.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 3271.921185] usb 1-2.4.2: Product: SimuCUBE
> [ 3271.921186] usb 1-2.4.2: Manufacturer: Granite Devices
> [ 3271.921187] usb 1-2.4.2: SerialNumber: 0123456789
> [ 3281.943990] input: Granite Devices SimuCUBE as /devices/pci0000:00/0000:00:09.0/0000:04:00.0/usb1/1-2/1-2.4/1-2.4.2/1-2.4.2:1.0/0003:16D0:0D5A.0016/input/input48
> [ 3281.944223] hid-generic 0003:16D0:0D5A.0016: unknown set_effect report layout
> [ 3281.944228] hid-generic 0003:16D0:0D5A.0016: input,hiddev2,hidraw15: USB HID v1.11 Joystick [Granite Devices SimuCUBE] on usb-0000:04:00.0-2.4.2/input0
>
> I spent some time looking at the code and also other ffb code in usbhid, but since I'm not really familiar with C I have a hard time figuring out why it doesn't work out of the box and how to fix this, but I'd be happy to help implementing/debugging it.
> For a start, it would be really nice to find out what is reported, what the report should look like and why it doesn't match.
Hi,
1. this eport is more appropriate for linux-input. You should put it
into CC
2. You indeed triggered this check:
/*
* Fill and check the pidff_usages
*/
static int pidff_init_fields(struct pidff_device *pidff, struct input_dev *dev)
{
int envelope_ok = 0;
if (PIDFF_FIND_FIELDS(set_effect, PID_SET_EFFECT, 1)) {
hid_err(pidff->hid, "unknown set_effect report layout\n");
return -ENODEV;
}
3. Your lsusb is incomplete (likely you need to run it as root), so
nobody can say what's wrong with your descriptors.
HTH
Oliver
next prev parent reply other threads:[~2019-06-17 10:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 10:35 Force Feedback support not recognized on Granite Devices Simucube Bernd Steinhauser
2019-06-17 10:57 ` Oliver Neukum [this message]
2019-06-17 11:36 ` Bernd Steinhauser
-- strict thread matches above, loose matches on Subject: below --
2019-06-17 11:46 Bernd Steinhauser
2020-02-05 18:54 ` Bernd Steinhauser
2022-06-26 9:59 ` Bernd Steinhauser
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=1560769038.8567.15.camel@suse.com \
--to=oneukum@suse.com \
--cc=linux-ml@bernd-steinhauser.de \
--cc=linux-usb@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.