summaryrefslogtreecommitdiff
path: root/keyboard/arrow_pad/README.md
diff options
context:
space:
mode:
authorIBNobody <ibnobody@gmail.com>2016-06-11 13:28:27 -0500
committerIBNobody <ibnobody@gmail.com>2016-06-11 13:28:27 -0500
commit50621a2e6a7d03add0c202e5b2698338c7fbbf5b (patch)
treed6f002712c22e8cf4523e04a9da889c7ec379d6b /keyboard/arrow_pad/README.md
parent26277dbdf40ba7247981361c956ea44c92bf76ea (diff)
parentd9e4dad0a828a8a904f44dda090a4d6d08fe2948 (diff)
Merge remote-tracking branch 'remotes/jackhumbert/master'
Diffstat (limited to 'keyboard/arrow_pad/README.md')
-rw-r--r--keyboard/arrow_pad/README.md24
1 files changed, 24 insertions, 0 deletions
diff --git a/keyboard/arrow_pad/README.md b/keyboard/arrow_pad/README.md
new file mode 100644
index 0000000000..f669ad6a12
--- /dev/null
+++ b/keyboard/arrow_pad/README.md
@@ -0,0 +1,24 @@
+arrow_pad 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/arrow_pad 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.
+
+### Default
+To build with the default keymap, simply run `make`.
+
+### Other Keymaps
+Several version of keymap are available in advance but you are recommended to define your favorite layout yourself. To define your own keymap create file named `<name>.c` in the keymaps folder, and see keymap document (you can find in top README.md) and existent keymap files.
+
+To build the firmware binary hex file with a keymap just do `make` with `KEYMAP` option like:
+```
+$ make KEYMAP=[default|jack|<name>]
+```
+Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder. \ No newline at end of file