Author | SHA1 | Message | Date |
---|---|---|---|
Ryan | 629cfc7f5e |
K-Type refactor (#9864)
* K-Type refactor * Declare QMK in product name again * Hopefully fix matrix scanning * Maybe this time * Partial (literally) RGB Matrix support * Put RGB_MATRIX_ENABLE into rgb keymap for now * Add ifdefs for RGB config * Set layer 1 to actually be layer 1... * Update keyboards/k_type/readme.md * Put all RGB config in keymap for now * Set SDB high? * Before `rgb_matrix_init()` would be best * User level, not keyboard * Combating dropped keys * Nope * Readme for RGB keymap * Remove custom matrix |
3 years ago |
fauxpark | d3bd1d893b | Ensure `PROGMEM` is present on default keymaps (#7836) | 4 years ago |
Drashna Jaelre | 0072fdd799 |
Cleanup Default Keymaps (#5442)
* Cleanup Default Keymaps to conform to QMK Firmware standards * Minor fixes * Revert some changes |
5 years ago |
fauxpark | 67adc29aa3 | Remove empty fn_actions[] | 5 years ago |
Kaleb Elwert | ab197af2ea |
Initial K-Type support (#1963)
* Initial K-Type support
* Copy PJRC_TEENSY_3_1 to work around watchdog issues
* K-Type: Remove bootloader offset in rules.mk
* Ensure matrix and scan quantum functions are called when needed
This is porting a fix from
|
6 years ago |