a080b5287f
* To avoid spurious CDC ACM instances when usint CDC ACM for something other than logging, move to the approach used by Zephyr of using a snippet to redirect console output to a CDC ACM node added by the snippet. Remove all the existing static CDC ACM nodes. * Add new `zmk-usb-logging` snippet that mirrors the upstream `cdc-acm-logging` snippet, but still does our extra USB logging configuration. * Updated logging docs accordingly. Co-authored-by: Cem Aksoylar <caksoylar@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| adv360pro-pinctrl.dtsi | ||
| adv360pro.dtsi | ||
| adv360pro.keymap | ||
| adv360pro.yaml | ||
| adv360pro.zmk.yml | ||
| adv360pro_left.dts | ||
| adv360pro_left_defconfig | ||
| adv360pro_right.dts | ||
| adv360pro_right_defconfig | ||
| board.cmake | ||
| Kconfig | ||
| Kconfig.board | ||
| Kconfig.defconfig | ||
| README.md | ||
Kinesis Advantage 360 Professional
This board definition provides upstream support for the Kinesis Advantage 360 Professional
Kinesis offer a specific custom configuration for the 360 Pro that references a customised version of ZMK with Advantage 360 Pro specific functionality and changes over base ZMK. The Kinesis fork is regularly updated to bring the latest updates and changes from base ZMK however will not always be completely up to date, some features such as new keycodes will not be immediately available on the 360 Pro after they are implemented in base ZMK.
When using this board definition some of the more advanced features (the indicator RGB leds) will not work, and Kinesis cannot provide customer service for usage of base ZMK. Likewise the ZMK community cannot provide support for either the Kinesis keymap editor, nor any usage of the Kinesis custom fork.