172e6a7030
* Extensible split data sync capability through transactions. - Split common transport has been split up between the transport layer and data layer. - Split "transactions" model used, with convergence between I2C and serial data definitions. - Slave matrix "generation count" is used to determine if the full slave matrix needs to be retrieved. - Encoders get the same "generation count" treatment. - All other blocks of data are synchronised when a change is detected. - All transmissions have a globally-configurable deadline before a transmission is forced (`FORCED_SYNC_THROTTLE_MS`, default 100ms). - Added atomicity for all core-synced data, preventing partial updates - Added retries to AVR i2c_master's i2c_start, to minimise the number of failed transactions when interrupts are disabled on the slave due to atomicity checks. - Some keyboards have had slight modifications made in order to ensure that they still build due to firmware size restrictions. * Fixup LED_MATRIX compile. * Parameterise ERROR_DISCONNECT_COUNT. |
||
|---|---|---|
| .. | ||
| keymaps | ||
| config.h | ||
| draculad.c | ||
| draculad.h | ||
| info.json | ||
| readme.md | ||
| rules.mk | ||
DracuLad
A 34-36 key split keyboard
- 36 keys, two of them can be replaced by rotary encoders making it support 34-36 keys and 2-4 encoders.
- bright RGB Underglow with WS2812B LEDs
- one SSD1306 OLED per side
- aggressive pinky stagger similar to the Kyria but with an alternative thumb cluster to raise comfort for large hands
- support for MX and Choc switches
- Keyboard Maintainer: MangoIV
- Hardware Supported: DracuLad PCBs and cases, the Pimoroni trackball
- Hardware Availability: MangoIV's GitHub
Make example for this keyboard (after setting up your build env):
make draculad:default
or for the version using the Pimoroni trackball:
make draculad:pimoroni
Flashing example for DFU and Caterina respectively (replace default with the name of your keymap):
make draculad:default:dfu
make draculad:default:flash
When flashing the first time using handedness by EEPROM, use the QMK guide for that topic.
See the build environment setup and the make instructions for more information. Brand new to QMK? Start with our Complete Newbs Guide.