GYR3101 Integration Notes: Difference between revisions
Initial Content. |
m Added Link to solution. |
||
| Line 1: | Line 1: | ||
Initial notes: | == Solution == | ||
The solution to supporting this and similar devices is to create a Generic HID Handler, as described here: [[Developers_Guide#9.2.8._Generic_HID_Interface]] | |||
==Initial notes:== | |||
Has same USB ID as Gyration Go mouse. 0c16:0002. | Has same USB ID as Gyration Go mouse. 0c16:0002. | ||
Revision as of 01:39, 28 June 2009
Solution
The solution to supporting this and similar devices is to create a Generic HID Handler, as described here: Developers_Guide#9.2.8._Generic_HID_Interface
Initial notes:
Has same USB ID as Gyration Go mouse. 0c16:0002.
All buttons except the very bottom buttons for binding emit HID. Will look further when I have my forensic analysis equipment.
I have attached an image here showing what part of the subsystem implements each currently decodable button as a colour coded chart:
- Red: Handled by the Keyboard HID event device
- Green: Handled by the Mouse HID event device
- Blue: Handled by the Mouse HID device
- Cyan: Must be decoded by reading hidraw device for keyboard
- Yellow: Must be decoded by reading hidraw device for mouse
Issues to deal with:
- We are missing explicit media/light buttons, so some context sensitive mode will have to be created in Orbiter.
- Get more data from analyser when I get it.
Onward and Upward!
-Thom