summaryrefslogtreecommitdiffstats
path: root/keyboard/kc60/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'keyboard/kc60/README.md')
-rw-r--r--keyboard/kc60/README.md9
1 files changed, 6 insertions, 3 deletions
diff --git a/keyboard/kc60/README.md b/keyboard/kc60/README.md
index fbc5ac9422..00d78d0a6b 100644
--- a/keyboard/kc60/README.md
+++ b/keyboard/kc60/README.md
@@ -2,12 +2,10 @@ KC60 (version 2.0) keyboard firmware
======================
## Quantum MK Firmware
-
For the full Quantum feature list, see [the parent README.md](/README.md).
## Building
-
-Download or clone the whole firmware and navigate to the keyboard/kc60 folder. Once your dev env is setup, you'll be able to type `make` to generate your .hex - you can then use the Teensy Loader to program your .hex file.
+Download or clone the whole firmware and navigate to the keyboard/kc60 folder. Once your dev env is setup, you'll be able to type `make` to generate your .hex - you can then use the Teensy Loader to program your .hex file.
Depending on which keymap you would like to use, you will have to compile slightly differently.
@@ -22,3 +20,8 @@ To build the firmware binary hex file with a keymap just do `make` with `KEYMAP`
$ make KEYMAP=[default|jack|<name>]
```
Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder.
+
+## WS2812 Support
+![Image of KC60 with RGB Underglow](keymaps/ws2812/ws2812_example.jpg)
+
+Build with WS2812 Support by running `make KEYMAP=ws2812`.