fix: use goosekb zmk config as starting point for firmware
This commit is contained in:
parent
1878cfe636
commit
b3b04d9847
10 changed files with 393 additions and 0 deletions
16
firmware/zmk-config/boards/shields/goose/Kconfig.defconfig
Normal file
16
firmware/zmk-config/boards/shields/goose/Kconfig.defconfig
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
if SHIELD_GOOSE_LEFT
|
||||
|
||||
config ZMK_KEYBOARD_NAME
|
||||
default "Cherry Goose"
|
||||
config USB_DEVICE_MANUFACTURER
|
||||
default "Pipshag"
|
||||
config ZMK_SPLIT_ROLE_CENTRAL
|
||||
default y
|
||||
|
||||
endif
|
||||
|
||||
if SHIELD_GOOSE_LEFT || SHIELD_GOOSE_RIGHT
|
||||
|
||||
config ZMK_SPLIT
|
||||
default y
|
||||
endif
|
||||
Loading…
Add table
Add a link
Reference in a new issue