portersky/xone_macos
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: mark rumble TX verified on hardware

Browse Source 
Rumble works from the Rumble button in the app; Phase 3 is complete.
Next up is Phase 4 (virtual HID gamepad).

Co-Authored-By: qwen3.8-27b@q3_k_xl: marked rumble verified
This commit is contained in:
portersky
2026-08-29 15:22:16 +02:00
parent 490b8af585
commit 73c026218d
2 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PLAN.md
+6 -6
View File
@@ -44,16 +44,16 @@ and exposes connected controllers as HID gamepads.
- Phase 3 (MT76 chip): register/EFUSE access, firmware load, radio init
(registers, crystal, MAC/BSSID, channel eval, beacon), pairing mode,
controller association, GIP handshake + auth. Verified end-to-end on
hardware: live controller input is shown in the app (RX data path).
hardware: live controller input is shown in the app (RX data path) and
rumble TX works from the app's Rumble button.
- C API + Swift app: async session (fast probe; firmware + radio on a worker
thread), state display (idle/starting/ready/error), controller list with
live input monitor, battery level, and a rumble test button.
Host to controller TX over the data path (rumble) is implemented; the dongle
LED is driven at chip level for pairing and client lifecycle. Phase 3 is
complete pending hardware confirmation of rumble. Next: Phase 4 (HID) and
Phase 5 (app polish); exposing the controller as a macOS HID gamepad is the
main user-visible gap.
The dongle LED is driven at chip level for pairing and client lifecycle.
Phase 3 is complete. Next: Phase 4 (virtual HID gamepad) and Phase 5 (app
polish); exposing the controller as a macOS HID gamepad is the main
user-visible gap.
## Directory Layout