Age | Commit message (Collapse) | Author |
|
|
|
* `EEP_RST` -> `EE_CLR`, default-ish keymaps
* `EEP_RST` -> `EE_CLR`, user keymaps
* `EEP_RST` -> `EE_CLR`, community layouts
* `EEP_RST` -> `EE_CLR`, userspace
* `EEP_RST` -> `EE_CLR`, docs & core
|
|
* `DEBUG` -> `DB_TOGG`, default-ish keymaps
* `DEBUG` -> `DB_TOGG`, user keymaps
* `DEBUG` -> `DB_TOGG`, community layouts
* `DEBUG` -> `DB_TOGG`, userspace
* `DEBUG` -> `DB_TOGG`, docs & core
|
|
|
|
* `KC_RSHIFT` -> `KC_RSFT`
* `KC_RCTRL` -> `KC_RCTL`
* `KC_LSHIFT` -> `KC_LSFT`
* `KC_LCTRL` -> `KC_LCTL`
|
|
* `KC_SLCK` -> `KC_SCRL`
* `KC_NLCK` -> `KC_NUM`
|
|
|
|
* `KC_PGDOWN` -> `KC_PGDN`
* `KC_PSCREEN` -> `KC_PSCR`
* `KC_SCOLON` -> `KC_SCLN`
* `KC_BSLASH` -> `KC_BSLS`
* `KC_BSPACE` -> `KC_BSPC`
|
|
|
|
* `KC__VOLDOWN` -> `KC_VOLD`
* `KC__VOLUP` -> `KC_VOLU`
* `KC__MUTE` -> `KC_MUTE`
* `KC_POWER` -> `KC_PWR`
|
|
* `KC_SYSREQ` -> `KC_SYRQ`
And one `KC_ALT_ERASE` -> `KC_ERAS`
* `KC_NONUS_BSLASH` -> `KC_NUBS`
* `KC_NUMLOCK` -> `KC_NUM`
* `KC_CLCK` -> `KC_CAPS`
* `KC_SCROLLLOCK` -> `KC_SCRL`
* `KC_LBRACKET` -> `KC_LBRC`
* `KC_RBRACKET` -> `KC_RBRC`
* `KC_CAPSLOCK` -> `KC_CAPS`
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* 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
|
|
|
|
|
|
Co-authored-by: James Young <18669334+noroadsleft@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
(#16655)
|
|
Added the keymap I have been using as a daily driver for the last month.
* good firmware 26 jan, best clicky mode stability so far
* modified to reflect master branch coding style
* further modified to reflect master branch coding style
* improving clicky stability, tuned down clicky delay duration
* changed name of keymap folder to use lowercase letters
|
|
|
|
|
|
|
|
|
|
|
|
* remove BOOTMAGIC_ENABLE=lite setting
* change keyboard BOOTMAGIC_ENABLE rules
Edits keyboard-level instances of `BOOTMAGIC_ENABLE = lite` to `BOOTMAGIC_ENABLE = yes`.
* change keyboard BOOTMAGIC_ENABLE inline comments
Edits keyboard-level BOOTMAGIC_ENABLE inline comments to "Enable Bootmagic Lite".
* change keymap BOOTMAGIC_ENABLE rules
Edits keymap-level instances of `BOOTMAGIC_ENABLE = lite` to `BOOTMAGIC_ENABLE = yes`.
* change keymap BOOTMAGIC_ENABLE inline comments
Edits/adds keymap-level BOOTMAGIC_ENABLE inline comments to read "Enable Bootmagic Lite".
* change layout/user BOOTMAGIC_ENABLE rules/comments
Edits instances of `BOOTMAGIC_ENABLE = lite` to `BOOTMAGIC_ENABLE = yes`.
Edits/adds keymap-level BOOTMAGIC_ENABLE inline comments to read "Enable Bootmagic Lite".
* update non-rules.mk BOOTMAGIC_ENABLE references in keyboards/
* remove docs references to Full Bootmagic
* convert data-driven Bootmagic Lite instances
* remove Bootmagic Lite bodge from data-driven generation
* Merge remote-tracking branch 'upstream/develop' into rm/bootmagic-full_q4a
* update docs/ja/config_options.md per mtei
* update docs/faq_misc.md per mtei
Remove remaining Full Bootmagic reference.
|
|
|
|
The old custom matrix code for Preonic rev3 was relying on the
`matrix_col_t` type, because the code actually reads the row pins and
assembles the state for whole columns, and then transposes the matrix in
the custom debouncing code. Restore that type (which is no longer
defined by the core QMK code) to make the custom matrix code work
properly (when `matrix_row_t` was used instead of `matrix_col_t`, the
state of two electrical rows was lost, and those electrical rows
corresponded to the bottom physical row, which did not work).
|
|
|
|
|
|
|
|
* Fix USB_6KRO_ENABLE compilation errors
* Add info to docs
* Rename define to be more accurate
* Remove unused rule
* Refixe docs
|
|
|
|
(#14623)
Co-authored-by: Ryan <fauxpark@gmail.com>
|
|
|
|
|
|
|
|
Co-authored-by: daskygit <32983009+daskygit@users.noreply.github.com>
|
|
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Jack Humbert <jack.humb@gmail.com>
|
|
|
|
|