diff options
author | climbalima <[email protected]> | 2016-12-03 17:15:22 -0500 |
---|---|---|
committer | climbalima <[email protected]> | 2016-12-03 17:15:22 -0500 |
commit | 59c54d651b4495f2790a9873e3aaa310d6ded787 (patch) | |
tree | 1191718cece98aa49813c2eae11798b544616661 /keyboards/maxipad/readme.md | |
parent | ae66f0d70214b8a5e81ecf5977619bcd4bf6f413 (diff) | |
parent | 102a830bbdb302eb0951ec7910ab7c9feae272d1 (diff) | |
download | qmk_firmware-59c54d651b4495f2790a9873e3aaa310d6ded787.tar.gz qmk_firmware-59c54d651b4495f2790a9873e3aaa310d6ded787.zip |
Merge https://github.com/climbalima/qmk_firmware
Diffstat (limited to 'keyboards/maxipad/readme.md')
-rw-r--r-- | keyboards/maxipad/readme.md | 22 |
1 files changed, 1 insertions, 21 deletions
diff --git a/keyboards/maxipad/readme.md b/keyboards/maxipad/readme.md index 606bacd75d..58ed5d718f 100644 --- a/keyboards/maxipad/readme.md +++ b/keyboards/maxipad/readme.md @@ -5,47 +5,27 @@ Maxipad keyboard firmware ## Quantum MK Firmware For the full Quantum feature list, see [the parent readme.md](/readme.md). -======= -## Quantum MK Firmware - -For the full Quantum feature list, see [the parent readme](/). - ->>>>>>> a06115df19a74d39b08758472b221e630c3680d3 - -## Building 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 -<<<<<<< HEAD -To build with the default keymap, simply run `make default`. -======= To build with the default keymap, simply run `make`. ->>>>>>> a06115df19a74d39b08758472b221e630c3680d3 ### 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. -<<<<<<< HEAD -======= -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. ->>>>>>> a06115df19a74d39b08758472b221e630c3680d3 To build the firmware binary hex file with a keymap just do `make` with a keymap like this: ``` $ make [default|jack|<name>] ``` -<<<<<<< HEAD -Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder. -======= Keymaps follow the format **__\<name\>.c__** and are stored in the `keymaps` folder. - ->>>>>>> a06115df19a74d39b08758472b221e630c3680d3 |