~ruther/qmk_firmware

Remove old OLED API code (#21651)

keycode aliases: work around ChibiOS ch.h include guard (#21497)

Fix layout offsets for a handful of boards (#21636)

CLI: Improve error messages when layout key matrix row/col is OOB (#21640)

Merge remote-tracking branch 'origin/master' into develop
Correct "less than" to "up to" in squeezing_avr?id=layers (#21639)

LED Matrix: driver naming cleanups (#21580)

Bluetooth: driver naming cleanups (#21624)

quantum.h: clean up process_keycode includes (#21579)

Merge remote-tracking branch 'origin/master' into develop
03b38409 — lalalademaxiya1 1 year, 11 months ago
Updated info.json of c2 pro (#21581)

Merge remote-tracking branch 'origin/master' into develop
[Keyboard] Add ANAVI Macro Pad 12 (#21547)

Merge remote-tracking branch 'origin/master' into develop
191b9899 — Álvaro Cortés 1 year, 11 months ago
[Keymap] update colemad crkbd (corne) keyboard (#21515)

Co-authored-by: Álvaro Cortés Devesa <alvarocortesdevesa@Alvaros-MacBook-Pro.local>
Merge remote-tracking branch 'origin/master' into develop
[Keyboard] add itstleo40 PCB (#21536)

Co-authored-by: jack <0x6a73@protonmail.com>
Co-authored-by: Drashna Jaelre <drashna@live.com>
32174abc — Stefan Kerkmann 1 year, 11 months ago
Update keyboard report descriptor for USB compliance (#21626)

Running the "HID Tests" suite of the USB 3 Command Verifier (USB3CV)
tool resulted in the following error:

(HID: 3.2.61) The report descriptor returned in response to a
GetDescriptor(Report) must be compliant with the HID specification.

Byte Number:   37h (  55d)
Data Field: 91 02
Mnemonic:  Output
Value: (Variable)
Errors: Error:   LOGICAL MAX MUST be bounded by Report Size

The error stems from the fact that logical minimum and maximum are
global items, which means that the next item in a report descriptor
inherits the value from the previously set value. In this case the
status leds item inherited the logical minimum (=0) and maximum (=255)
from the keycodes item. As the status leds set a report size of 1 bit,
wich can only hold a boolean, it becomes clear that this range would
never fit.

The fix is straightforward, we just define a appropriate logical maximum
(=1), the mismatch is solved and our keyboard now passes the compliance
tests. Defining the logical minimum is redundant in this case but is
kept to form a logical block.
Merge remote-tracking branch 'origin/master' into develop
[Keyboard] Add Divine keyboard (#21593)

Next