I believe the second line of the rule Marc attached might be obsolete;
either way, it isn't relevant to the scope of this issue.
Attached a dump of the udev database with both a wired controller and a
wireless receiver for the controller connected.
I'm a little nervous about creating a rule based on device class,
because the controller/receiver has generic HID endpoints that are used
to program it. I don't believe these will match any particular device
class. In addition, the controller's firmware will be updated on the fly
by the Steam client, which might change the endpoint count and types in
the future.
However product IDs might be a good fit; here are the four PIDs that the
current model of controllers will report during everyday use:
D0G_PID = 0x1102,
D0GGLE_PID = 0x1142,
D0G_BOOTLOADER_PID = 0x1002,
D0GGLE_BOOTLOADER_PID = 0x1042,
That being said, there aren't any other USB devices reporting a Valve
Corp. USB vendor ID of 0x28DE in the wild right now, but there will be
soon when eg. the controllers for the HTC Vive VR headset ship out to
the world, so a rule matching any Valve-owned device would be more
future-proof.
** Attachment added: "udev.txt"
https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1498655/+attachment/4474540/+files/udev.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1498655
Title:
Steam Controller support: need read-write access to Valve-owned input
event device nodes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/steam/+bug/1498655/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
