3f5dc47296
* Use polled waiting on platforms that support it Due to context switching overhead waiting a very short amount of time on a sleeping thread is often not accurate and in fact not usable for timing critical usage i.e. in a driver. Thus we use polled waiting for ranges in the us range on platforms that support it instead. The fallback is the thread sleeping mechanism. This includes: * ARM platforms with CYCCNT register (ARMv7, ARMv8) this is incremented at CPU clock frequency * GD32VF103 RISC-V port with CSR_MCYCLE register this is incremented at CPU clock frequency * RP2040 ARMv6 port which uses the integrated timer peripheral which is incremented with a fixed 1MHz frequency * Use wait_us() instead of chSysPolledDelayX ...as it is powered by busy waiting now. * Add chibios waiting methods test bench |
||
|---|---|---|
| .. | ||
| blackpill_f401 | ||
| blackpill_f411 | ||
| blackpill_f411_tinyuf2 | ||
| bluepill | ||
| elite_c | ||
| evb_wb32f3g71 | ||
| evb_wb32fq95 | ||
| 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 | ||
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.