Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Move RGBLight animations to data driven (#21635) | Ryan | 2023-08-23 | 1 | -1/+13 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Move RGBLight animations to data driven, 0-9 * Move RGBLight animations to data driven, A * Move RGBLight animations to data driven, B * Move RGBLight animations to data driven, C * Move RGBLight animations to data driven, D * Move RGBLight animations to data driven, E * Move RGBLight animations to data driven, F * Move RGBLight animations to data driven, G * Move RGBLight animations to data driven, H * Move RGBLight animations to data driven, handwired * Move RGBLight animations to data driven, I * Move RGBLight animations to data driven, J * Move RGBLight animations to data driven, K * Move RGBLight animations to data driven, L * Move RGBLight animations to data driven, M * Move RGBLight animations to data driven, N * Move RGBLight animations to data driven, O * Move RGBLight animations to data driven, P * Move RGBLight animations to data driven, Q * Move RGBLight animations to data driven, R * Move RGBLight animations to data driven, S * Move RGBLight animations to data driven, T * Move RGBLight animations to data driven, U * Move RGBLight animations to data driven, V * Move RGBLight animations to data driven, W * Move RGBLight animations to data driven, X * Move RGBLight animations to data driven, Y * Move RGBLight animations to data driven, Z * Fix incorrect placement * Fix build failures and mismatches | ||||
* | Move `RGBLED_NUM` to data driven (#21278) | Ryan | 2023-06-18 | 1 | -0/+3 |
| | |||||
* | Move remaining `LAYOUT`s to data driven (#20422) | Ryan | 2023-04-15 | 1 | -3/+248 |
| | |||||
* | Migrate `rgblight.pin` and `RGB_DI_PIN` to `ws2812.pin` (#20303) | Ryan | 2023-04-06 | 1 | -0/+3 |
| | |||||
* | Move backlight config to data driven (#19910) | Ryan | 2023-02-26 | 1 | -0/+4 |
| | |||||
* | Move Bootmagic config to data driven (#19860) | Ryan | 2023-02-17 | 1 | -0/+3 |
| | |||||
* | Migrate `MCU` and `BOOTLOADER` to data-driven (#19529) | Ryan | 2023-02-08 | 1 | -0/+2 |
| | |||||
* | Move keyboard USB IDs and strings to data driven: D (#17814) | Ryan | 2022-07-29 | 1 | -0/+6 |
| | |||||
* | Remove width, height and key_count from info.json (#14274) | Ryan | 2021-09-12 | 1 | -2/+0 |
| | |||||
* | Keyboard: Updated info.json for Duck Jetfire (#3866) | noroadsleft | 2018-09-13 | 1 | -8/+8 |
| | | | | | | | | * Updated info.json for Duck Jetfire Generated a new info.json file. @mechmerlin asked my help in debugging this file. Firmware works as expected if built from source, but not if built from the Configurator. * Corrected the position of the arrow keys in LAYOUT_all | ||||
* | Keyboard: Duck Jetfire QMK Support (#3752) | MechMerlin | 2018-08-25 | 1 | -0/+16 |
* Initial Commit Port from xauser's jetfire code. Does not compile yet * fix up keymap from uint8 to uin16 * update rules file to contain custom matrix * Good stopping point Still lots of compile errors but I'm getting there. * fix a few more compile errors * move a few functions around to help with compiling * Finally got it all to compile * Get rid of that old KEYMAP macro * edit readme * Put my name everywhere and some minor code clean ups * start to remove that kc nonsense * fix keymap compilation issues * add reset key info * better human readable formatting * match the duck default layout * add confgurator support * clarify reset key * might be a good idea to use the correct pin * get the riight keycode for RGB * include an ALL layout * I tried to fix the formatting....sigh * add functons to ensure Configurator compile-ability * move jetfire to duck directory * Moved and renamed things as per Drashna's PR comments as his back was hurting as he reviewed this |