summaryrefslogtreecommitdiff
path: root/keyboards/miuni32/readme.md
diff options
context:
space:
mode:
authorJack Humbert <jack.humb@gmail.com>2017-04-04 13:41:50 -0400
committerGitHub <noreply@github.com>2017-04-04 13:41:50 -0400
commitffffd1b6c12c44ca85cd27f63662ab7736177be6 (patch)
tree3dffb2ea18b75bd65e62d1bcc7469039b455c6d7 /keyboards/miuni32/readme.md
parentd75a44a02b5047510cfd25fab5a839537efdbfb7 (diff)
parent8e7be3adda577ab58ed942d83e0d2ebd4ab07f88 (diff)
Merge pull request #1207 from bigtunaIO/master
Add Bigtuna.io Miuni32
Diffstat (limited to 'keyboards/miuni32/readme.md')
-rw-r--r--keyboards/miuni32/readme.md28
1 files changed, 28 insertions, 0 deletions
diff --git a/keyboards/miuni32/readme.md b/keyboards/miuni32/readme.md
new file mode 100644
index 0000000000..36696ddbcb
--- /dev/null
+++ b/keyboards/miuni32/readme.md
@@ -0,0 +1,28 @@
+miuni32 keyboard firmware
+======================
+
+## 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/miuni32 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 default`.
+
+### 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.