

IdVendor 0x0810 Personal Communication Systems, Inc.īInterfac eClass 3 Human Interface Devices

It's the same basic problem, but with a different product.īus 003 Device 003: ID 0810:0002 Personal Communication Systems, Inc.īDeviceClass 0 (Defined at Interface level)

Sorry if this is a duplicate of Paul's bug, I wasn't sure. Unfortunately I'm a bit over my head here, and I don't know how to write a patch. c, and setting the "multi input" quirk produced the correct behaviour. Adding the vendor and product IDs to drivers/ usb/input/ hid-core. (Vendor ID 0x0810) Twin USB Gamepad (Product ID 0x0002).Īs detailed in Paul's bug report, the two controllers were muxed together as one. I have a Personal Communications Systems, Inc. This bug is very similar to bug #106622 reported by Paul Zaremba, but affects a different device.
