Kimplul
Kimplul
Completely different functionality, mainly. The init driver is responsible for initializing the wheel, whereas the main driver is responsible for handling the actual FFB commands. It turns out that essentially...
Right, yes, I meant that each driver would need the same init code, and to avoid duplicating it into each driver (T150/T300/etc) we kept the init as a separate driver....
> My filter is usb.src == "1..0" or usb.dst == "1..0" This might be too restrictive. The last number, which you've set to zero here, is the USB endpoint number....
> It does not, I did try it at the time, it's mentioned there: Right, sorry, should've read your issue more thoroughly. Anycase, I added a couple captures with the...
Hi, sorry for the delay. Here's where I'm at at the moment: Ignoring endpoint 2, which is used for button input etc. I couldn't really find any info in the...
In the `dmesg` log the wheel reports itself as having PID `0xb66e`, but you say `lsusb` shows it as `0xb66d`. `0xb66d` is the ID the wheel shows up as when...
PS4 mode support is sort of work in progress over in the `ps4` branch, but I recommend sticking to PS3 mode for now. Correct me if I'm wrong, but the...
`jstest-gtk` is in Ubuntu's repos, so running `sudo apt install jstest-gtk` should install all dependencies. If you want to manually compile `sigc++`, seems that you need `xsltproc`, maybe some other...
Right, that's good. I can't get steam to recognise the wheel as a gamepad at all, is it still being recognised as a gamepad by your steam?
Alright, and what does FH5 do?