1
0
Fork 0
forked from forks/qmk_firmware
qmk_firmware/keyboards/maxipad
2016-11-16 19:49:38 -05:00
..
keymaps/default should have fixed conflixed 2016-11-16 19:49:38 -05:00
config.h should have fixed conflixed 2016-11-16 19:49:38 -05:00
Makefile should have fixed conflixed 2016-11-16 19:49:38 -05:00
maxipad.c Updated my repo to current qmk 2016-11-16 19:18:54 -05:00
maxipad.h Updated my repo to current qmk 2016-11-16 19:18:54 -05:00
readme.md Merge https://github.com/climbalima/qmk_firmware 2016-11-16 19:26:38 -05:00
rules.mk Updated my repo to current qmk 2016-11-16 19:18:54 -05:00

maxipad keyboard firmware

Quantum MK Firmware

<<<<<<< HEAD For the full Quantum feature list, see the parent readme.

For the full Quantum feature list, see the parent readme.md.

bce6e52391

Building

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.

bce6e52391

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.

<<<<<<< HEAD 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.

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/

bce6e52391