ZMK Firmware Fork to add Forgejo Workflow Support
With newlib_libc enabled, a warning was printed for this memcpy. uuid is a `bt_uuid_128`, while BT_UUID_GATT_CCC is only `bt_uuid_16`. Fixes #808. Full warning: [53/272] Building C object CMakeFiles/app.dir/src/split/bluetooth/central.c.obj In file included from /home/okke/.local/zephyr-sdk-0.11.2/arm-zephyr-eabi/arm-zephyr-eabi/sys-include/string.h:180, from /home/okke/dev/zmk/zephyr/include/bluetooth/bluetooth.h:21, from ../../src/split/bluetooth/central.c:9: ../../src/split/bluetooth/central.c: In function 'split_central_discovery_func': ../../src/split/bluetooth/central.c:130:9: warning: '__builtin_memcpy' forming offset [5, 17] is out of the bounds [0, 4] of object '({anonymous})' with type 'struct bt_uuid_16[1]' [-Warray-bounds] 130 | memcpy(&uuid, BT_UUID_GATT_CCC, sizeof(uuid)); | ^~~~~~ /home/okke/dev/zmk/zephyr/include/bluetooth/uuid.h:72:45: note: '({anonymous})' declared here 72 | ((struct bt_uuid *) ((struct bt_uuid_16[]) {BT_UUID_INIT_16(value)})) | ^ /home/okke/dev/zmk/zephyr/include/bluetooth/uuid.h:372:2: note: in expansion of macro 'BT_UUID_DECLARE_16' 372 | BT_UUID_DECLARE_16(BT_UUID_GATT_CCC_VAL) | ^~~~~~~~~~~~~~~~~~ ../../src/split/bluetooth/central.c:130:23: note: in expansion of macro 'BT_UUID_GATT_CCC' 130 | memcpy(&uuid, BT_UUID_GATT_CCC, sizeof(uuid)); |
||
---|---|---|
.devcontainer | ||
.github | ||
.vscode | ||
app | ||
docs | ||
.clang-format | ||
.gitattributes | ||
.gitignore | ||
.pre-commit-config.yaml | ||
AUTHORS | ||
CODE_OF_CONDUCT.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
LICENSE | ||
README.md |
Zephyr™ Mechanical Keyboard (ZMK) Firmware
ZMK Firmware is an open source (MIT) keyboard firmware built on the Zephyr™ Project Real Time Operating System (RTOS). ZMK's goal is to provide a modern, wireless, and powerful firmware free of licensing issues.
Check out the website to learn more: https://zmkfirmware.dev/
You can also come join our ZMK Discord Server
To review features, check out the feature overview. ZMK is under active development, and new features are listed with the enhancement label in GitHub. Please feel free to add 👍 to the issue description of any requests to upvote the feature.