Hi Peter On Tue, Nov 13, 2012 at 3:53 AM, Peter Olson <peter.olson@xxxxxxxxx> wrote: > RE: flashing LEDs, the LEDs are always flashing every connect. I > haven't had them once switch from all-flashing to having only LED1 (or > just any single LED) lit. Also, I've never heard of / used the sysfs > API, so I don't know how to test controlling the LEDs directly. That doesn't sound right. Looks like they changed the protocol with the new Wii Remotes. Or at least our implementation is not compatible with them. > RE: dolphin-emu, Ok, after we have all the kinks worked out here, I'll > approach them separately to try and get their code updated. > > RE: xwiishow, I use it by executing [xwiishow list] as a regular user. > I tried it as root once, just out of curiosity, but that made no > difference. > > $ ls -l /sys/bus/hid/devices/ > total 0 > lrwxrwxrwx 1 root root 0 Nov 11 22:00 0003:046D:C068.0003 -> > ../../../devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.8/4-1.8:1.0/0003:046D:C068.0003 > lrwxrwxrwx 1 root root 0 Nov 11 22:00 0003:046D:C068.0004 -> > ../../../devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.8/4-1.8:1.1/0003:046D:C068.0004 > lrwxrwxrwx 1 root root 0 Nov 11 22:00 0003:046D:C31C.0001 -> > ../../../devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.5/4-1.5:1.0/0003:046D:C31C.0001 > lrwxrwxrwx 1 root root 0 Nov 11 22:00 0003:046D:C31C.0002 -> > ../../../devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.5/4-1.5:1.1/0003:046D:C31C.0002 > lrwxrwxrwx 1 root root 0 Nov 12 18:27 0005:057E:0330.0009 -> > ../../../devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1/3-1.1:1.0/bluetooth/hci0/hci0:11/0005:057E:0330.0009 Yeah, the last device is the right device. It's the VID/PID information, not the btaddr, you're right. > $ xwiishow /sys/bus/hid/devices/0005:057E:0330.0009 > Cannot open core iface '/sys/bus/hid/devices/0005:057E:0330.0009' err:-13 That's EACCES, you need to run it as root. > $ sudo xwiishow /sys/bus/hid/devices/0005:057E:0330.0009 > Cannot open core iface '/sys/bus/hid/devices/0005:057E:0330.0009' err:-22 22 is EINVAL. After looking into libxwiimote I know understand the problem. I use the VID/PID information to detect the devices there. That doesn't work if you use other IDs. Can you change ./xwiimote/lib/xwiimote.h line 32/33: #define XWII_ID_VENDOR>->-------0x057e #define XWII_ID_PRODUCT>>-------0x0306 to: #define XWII_ID_VENDOR>->-------0x057e #define XWII_ID_PRODUCT>>-------0x0330 This should work. If it still returns EINVAL, then simply remove all tests in ./xwiimote/lib/*.c that use these IDs. They're only used for forward-compatibility if the IDs change and we modify APIs. > Speaking of fun dmesg messages, I got this when I tried re-connecting > my wiimote after connecting and disconnecting it as shown just above: > http://pastebin.com/ehjvfpcf Yeah, the linux bluetooth kernel modules have a lot of bugs in the HID layer. I reported them like 2 years ago but they keep on breaking these. It's like if you connect more than 1 device, their module shows these bugs. It's all on my TODO list but I currently have no time to fix the Bluetooth layer. Feel free to report this to linux-bluetooth@xxxxxxxxxxxxxxx. This isn't related to this driver at all. I am sorry for that. > I get a similar looking dump if I try connecting again, and now > bluetooth is just confused on my machine. I'll have to reboot before > trusting any further output from the computer on this mater. > > Hopefully the early part of this email will help you solve the general > issue (with xwiishow and such). Please let me know if I should worry > about the crash-dump in the later part of this email, or if I should > just reboot and ignore it for now. Easiest way is simply rebooting and then retrying it. But with the changes to xwiimote above, you should now be able to use xwiishow. Thanks David -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
