docs: mark rumble TX as implemented
Update PLAN.md and README.md current status: host to controller TX (rumble) is implemented and pending hardware confirmation; the dongle LED is driven at chip level, so no data path LED work remains. Co-Authored-By: qwen3.8-27b@q3_k_xl: updated status docs
This commit is contained in:
@@ -47,11 +47,13 @@ and exposes connected controllers as HID gamepads.
|
||||
hardware: live controller input is shown in the app (RX data path).
|
||||
- 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.
|
||||
live input monitor, battery level, and a rumble test button.
|
||||
|
||||
Remaining for Phase 3: host to controller TX over the data path (rumble,
|
||||
LED). Then Phase 4 (HID) and Phase 5 (app polish); exposing the controller
|
||||
as a macOS HID gamepad is the main user-visible gap.
|
||||
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.
|
||||
|
||||
## Directory Layout
|
||||
|
||||
|
||||
Reference in New Issue
Block a user