summaryrefslogtreecommitdiff
path: root/keyboards/maxipad/readme.md
diff options
context:
space:
mode:
authorxyverz2016-11-16 22:36:36 -0800
committerxyverz2016-11-16 22:36:36 -0800
commitb493f6a4ed14e74c268ae3d7a07577591fe71cc7 (patch)
tree0da986aa45733b08c6b8c379658abd5e0a1fb8a7 /keyboards/maxipad/readme.md
parent8dd422ffe1a84416dd4a8d38878979f5b7bbd51b (diff)
parentc38b3e3be93a8b4f520212117b6498a288d67751 (diff)
Merge remote-tracking branch 'upstream/master'
Diffstat (limited to 'keyboards/maxipad/readme.md')
-rw-r--r--keyboards/maxipad/readme.md28
1 files changed, 28 insertions, 0 deletions
diff --git a/keyboards/maxipad/readme.md b/keyboards/maxipad/readme.md
new file mode 100644
index 000000000..ab7b122fe
--- /dev/null
+++ b/keyboards/maxipad/readme.md
@@ -0,0 +1,28 @@
+## Quantum MK Firmware
+
+For the full Quantum feature list, see [the parent readme](/).
+
+
+## Building
+
+Download or clone the whole firmware and navigate to the keyboards/maxipad 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 a folder with the name of your keymap in the keymaps folder, and see keymap documentation (you can find in top readme.md) and existant keymap files.
+
+To build the firmware binary hex file with a keymap just do `make` with a keymap like this:
+
+```
+$ make [default|jack|<name>]
+```
+
+Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder.
+