@Ax0_0 absolutely correct
@Gavin this is a firmware issue.
ok, because your not getting "HID class started." this indicates the device is not being recognised as a standard HID device.
this is likely to be one of :
- power, if devices requests too much power it wont be accepted.
- its not class compliant, i.e. to use it you need to use devices drivers when you use on mac/pc
- its got an internal hub e.g. a keyboard with an integrated mouse, might present itself as two devices (keyboard and mouse) via a hub - axoloti does not support hubs
- some odd issue with the communication with that mouse
Ive not see this with mice before, but honestly, thats probably more down to number of users attaching mice... but we have had all of these issues reported with MIDI devices.
I'm a bit surprised you don't get the device information printed, as im pretty sure we print that prior to determining if its a handled device or not. that, plus, you say the light not coming on, makes me wonder if its a power issue... but seems odd for a mouse
perhaps you can review the above, and think if any may apply.
if its a firmware issue, then the USB handling has been completely rewritten for the next release of axoloti (sorry, no date for that). This might help , and its also supports hubs , which would also help power issues (as you could use a powered hub, to supply more juice)
sorry, no immediate help...
hmm, not sure... id need to test this, not tried with any mouse i have...
I think others have had the mouse code working, but id like to try myself before commenting.
as I said above, im not sure how much use this has got...
did you look at the help patch, i must admit its more complex than id have expected... i.e. the data appears to be 'packed'