3f9d464412
* usb_device_state: add idle_rate, led and protocol Previously all usb drivers and platform implementations (expect for our oddball atsam) tracked the same two global variables: - keyboard_protocol: to indicate if we are in report or boot protocol - keyboard_idle: for the idle_rate of the keyboard endpoint And a local variable that was exposed trough some indirection: - keyboard_led_state: for the currently set indicator leds (caps lock etc.) These have all been moved into the usb_device_state struct wich is accessible by getters and setters. This reduces code duplication and centralizes the state management across platforms and drivers. Signed-off-by: Stefan Kerkmann <karlk90@pm.me> * usb_device_state: reset protocol on reset The usb hid specification section 7.2.6 states: When initialized, all devices default to report protocol. However the host should not make any assumptions about the device’s state and should set the desired protocol whenever initializing a device. Thus on reset we should always do exactly that. Signed-off-by: Stefan Kerkmann <karlk90@pm.me> * keyboards: fix oversize warnings Signed-off-by: Stefan Kerkmann <karlk90@pm.me> --------- Signed-off-by: Stefan Kerkmann <karlk90@pm.me> |
||
|---|---|---|
| .. | ||
| keymaps/default | ||
| keyboard.json | ||
| matrix_diagram.md | ||
| readme.md | ||
Ellora65
65% With Macro Column, Encoder, and OLED
- Keyboard Maintainer: Kiko
- Hardware Supported: KL-65 PCB
- Hardware Availability: https://www.kikoslab.com
Bootloader
Enter the bootloader in 3 ways:
- Bootmagic reset: Hold down the key at (1,0) in the matrix (escape key) and plug in the keyboard
- Physical reset button: Briefly press the button on the back of the PCB
- Keycode in layout: Press the key mapped to
QK_BOOTif it is available
Make example for this keyboard (after setting up your build environment):
make kikoslab/ellora65:default
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.