summaryrefslogtreecommitdiff
path: root/keyboards/maxipad/readme.md
diff options
context:
space:
mode:
authorDamien2016-12-09 19:44:03 +0100
committerGitHub2016-12-09 19:44:03 +0100
commit13c4080a1d77cb1dfdf48df8a42e78b9dc483912 (patch)
tree66fd988d98a32e1437fbc6cb80bee03c056722a7 /keyboards/maxipad/readme.md
parenta849bdc5811b2bb69df8e3b0948c8e81c0dfa9d4 (diff)
parent985a091a739c99736d5b17de5161831488dbc219 (diff)
Merge pull request #13 from jackhumbert/master
Merged from qmk
Diffstat (limited to 'keyboards/maxipad/readme.md')
-rw-r--r--keyboards/maxipad/readme.md29
1 files changed, 29 insertions, 0 deletions
diff --git a/keyboards/maxipad/readme.md b/keyboards/maxipad/readme.md
new file mode 100644
index 000000000..861ea2b07
--- /dev/null
+++ b/keyboards/maxipad/readme.md
@@ -0,0 +1,29 @@
+Maxipad keyboard firmware
+
+## Quantum MK Firmware
+
+For the full Quantum feature list, see [the parent readme.md](/readme.md).
+
+If you are using a pro micro then make sure to enable USE_PRO_MICRO in the makefile
+Change the config.h pinout to match your mcu!!
+
+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 file named `<name>.c` 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 a keymap like this:
+
+```
+$ make [default|jack|<name>]
+```
+
+Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder.