summaryrefslogtreecommitdiff
path: root/keyboards/kinesis/readme.md
diff options
context:
space:
mode:
authorJoshua T <joshua@sonofone.net>2016-07-26 01:49:24 -0500
committerJoshua T <joshua@sonofone.net>2016-07-26 01:49:24 -0500
commit5607b716ba0ec7002f29244f24aa8999b9511061 (patch)
treebdd1255faa369d1e9bf1959d96b25ed857916ff5 /keyboards/kinesis/readme.md
parent876a6bdd4ca9033972d0a2d8c0c563cc6d7d9e7e (diff)
parentf9aadd17e8fce17fe1e135cf8022e71a35ae5adf (diff)
Merge remote-tracking branch 'upstream/master'
Diffstat (limited to 'keyboards/kinesis/readme.md')
-rw-r--r--keyboards/kinesis/readme.md42
1 files changed, 42 insertions, 0 deletions
diff --git a/keyboards/kinesis/readme.md b/keyboards/kinesis/readme.md
new file mode 100644
index 0000000000..a990f9cb99
--- /dev/null
+++ b/keyboards/kinesis/readme.md
@@ -0,0 +1,42 @@
+kinesis-advantage keyboard firmware
+======================
+
+## Kinesis specific information
+This is a port of https://github.com/alvicstep/tmk_keyboard,
+which is a fork of https://github.com/wjanssens/tmk_keyboard,
+which is based on work from https://github.com/chrisandreae/keyboard-firmware
+
+If you replace the kinesis CPU as described in the doc folder, then this code should allow you to use QMK.
+I've tested with a Teensy 2++, remember to change the CPU if you use a 32u4 instead.
+
+Not yet implemented:
+- Kinesis EEProm reading or writing
+- Audio - this should be simple if we remove hardcoded pins from audio.h and switch to E7
+
+
+
+## Quantum MK Firmware
+
+For the full Quantum feature list, see [the parent readme.md](/doc/readme.md).
+
+## Building
+
+Download or clone the whole firmware and navigate to the keyboards/kinesis-advantage 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 `keymap` option like:
+
+```
+$ make keymap=[default|jack|<name>]
+```
+
+Keymaps follow the format **__keymap.c__** and are stored in folders in the `keymaps` folder, eg `keymaps/my_keymap/`