aboutsummaryrefslogtreecommitdiffstats
path: root/keyboards/frosty_flake/readme.md
diff options
context:
space:
mode:
authorXyverz <xyverz@gmail.com>2017-04-02 14:49:39 -0700
committerXyverz <xyverz@gmail.com>2017-04-02 14:49:39 -0700
commitc034b61b1abb2bf23187abae562bf53916c60fa1 (patch)
treed36aa00c7ae93ce144445638b61269d3a0dd5f50 /keyboards/frosty_flake/readme.md
parent787304647961f4cb654188ddb88c22dd7991ab87 (diff)
parent3448d5d4874a2775f85320a2be69edd241575d46 (diff)
downloadfirmware-c034b61b1abb2bf23187abae562bf53916c60fa1.tar.gz
firmware-c034b61b1abb2bf23187abae562bf53916c60fa1.tar.bz2
firmware-c034b61b1abb2bf23187abae562bf53916c60fa1.zip
Merge remote-tracking branch 'upstream/master'
Diffstat (limited to 'keyboards/frosty_flake/readme.md')
-rw-r--r--keyboards/frosty_flake/readme.md32
1 files changed, 32 insertions, 0 deletions
diff --git a/keyboards/frosty_flake/readme.md b/keyboards/frosty_flake/readme.md
new file mode 100644
index 000000000..ff440e33b
--- /dev/null
+++ b/keyboards/frosty_flake/readme.md
@@ -0,0 +1,32 @@
+frosty_flake keyboard firmware
+======================
+
+This is the firmware for Rev. 20140521 of the Frosty Flake controller by [Bathroom Epiphanies](http://bathroomepiphanies.com/controllers/), a replacement controller for the [Cooler Master Quick Fire Rapid](http://www.coolermaster.com/peripheral/keyboards/quickfirerapid/).
+
+The code was adapted from the [BathroomEpiphanies TMK Firmware](https://github.com/BathroomEpiphanies/epiphanies_tmk_keyboard/tree/master/be_controllers), but has been cleaned up to match the [schematic](https://deskthority.net/wiki/File:Frosty_Flake_Schematics.pdf) and gone through some minor refactoring for QMK.
+
+## 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/frosty_flake 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.