9632360caa
* Add ARRAY_SIZE and CEILING utility macros * Apply a coccinelle patch to use ARRAY_SIZE * fix up some straggling items * Fix 'make test:secure' * Enhance ARRAY_SIZE macro to reject acting on pointers The previous definition would not produce a diagnostic for ``` int *p; size_t num_elem = ARRAY_SIZE(p) ``` but the new one will. * explicitly get definition of ARRAY_SIZE * Convert to ARRAY_SIZE when const is involved The following spatch finds additional instances where the array is const and the division is by the size of the type, not the size of the first element: ``` @ rule5a using "empty.iso" @ type T; const T[] E; @@ - (sizeof(E)/sizeof(T)) + ARRAY_SIZE(E) @ rule6a using "empty.iso" @ type T; const T[] E; @@ - sizeof(E)/sizeof(T) + ARRAY_SIZE(E) ``` * New instances of ARRAY_SIZE added since initial spatch run * Use `ARRAY_SIZE` in docs (found by grep) * Manually use ARRAY_SIZE hs_set is expected to be the same size as uint16_t, though it's made of two 8-bit integers * Just like char, sizeof(uint8_t) is guaranteed to be 1 This is at least true on any plausible system where qmk is actually used. Per my understanding it's universally true, assuming that uint8_t exists: https://stackoverflow.com/questions/48655310/can-i-assume-that-sizeofuint8-t-1 * Run qmk-format on core C files touched in this branch Co-authored-by: Stefan Kerkmann <karlk90@pm.me> |
||
|---|---|---|
| .. | ||
| blackpill_f401 | ||
| blackpill_f411 | ||
| blackpill_f411_tinyuf2 | ||
| bluepill | ||
| bluepill_f103c6 | ||
| elite_c | ||
| evb_wb32f3g71 | ||
| evb_wb32fq95 | ||
| kb2040 | ||
| keymaps | ||
| nucleo_l432kc | ||
| promicro | ||
| proton_c | ||
| rp2040 | ||
| sipeed_longan_nano | ||
| stm32f0_disco | ||
| stm32f405_feather | ||
| teensy_2 | ||
| teensy_2pp | ||
| teensy_32 | ||
| teensy_35 | ||
| teensy_lc | ||
| config.h | ||
| info.json | ||
| onekey.c | ||
| onekey.h | ||
| readme.md | ||
| rules.mk | ||
readme.md
onekey
Custom handwired one key keyboard. See each individual board for pin information.
- Keyboard Maintainer: QMK Community
- Hardware Supported: Blackpill F401/F411, Bluepill, Elite-C, Pro Micro, Proton C, Sipeed Longan Nano, STM32F0 Disco, Teensy 2.0, Teensy++ 2.0, Teensy LC, Teensy 3.2
- Hardware Availability: n/a
Make example for this keyboard (after setting up your build environment):
make handwired/onekey:default
Flashing example for this keyboard:
make handwired/onekey:default:flash
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.