Open skraus-dev opened 1 year ago
Perhaps this should be moved into a separate doc (just like the compatibility map). This makes it easier to collaborate by editing and submit pull requests. Also: Maybe all those supplemental docs should go into some subdir.
Perhaps this should be moved into a separate doc (just like the compatibility map).
The steps to download / extract the files from windows cherry utility were moved into a new document, RESEARCH.md
This makes it easier to collaborate by editing and submit pull requests.
Agree. For specific functionality that are subject to discuss, I would like to keep logs/notes inside the respective issues. When they reach a level of agreement / deeper understanding, they can be written down in
https://github.com/skraus-dev/cherryrgb-rs/blob/master/docs/PROTOCOL.md
Also: Maybe all those supplemental docs should go into some subdir.
At first I wanted to keep them in the top-level.. but at this point its starting to make sense to have them seperated. Done ;)
The Cherry Utility for Windows holds some hardcoded per-device defaults, which describe each key and mapping.
See RESEARCH.md
Fetch device state
The function
fetch_device_state
(https://github.com/skraus-dev/cherryrgb-rs/blob/master/cherryrgb/src/lib.rs#L246) is currently just replaying captured requests that were sniffed.Guesses, without having digged deeper into it
NOTE: The name
fetch_device_state
might be misleading - it could be very well something along the lines ofset_device_state
orset_key_config/mapping
Here is a captuire of the transfers: