gitbot
/
qmk_firmware
mirror of https://github.com/qmk/qmk_firmware
0
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
qmk_firmware/keyboards/handwired/woodpad
History
Drashna Jaelre 17200f4712 Clean up and tweaks of drashna keymaps and userspace (#2200) 
* Minor tweaks

	modified:   users/drashna/drashna.c

* Fix Workman ASCII art

* Add OSM for shifts

* Make Viterbi's 00 code consistant

* Minor Cleanup off Userspace

* Change Tapping Term on Ergodox

* Re-add EEPROM code

* Minor updates and tweaks

* Use QMK_H variables to make keymaps more universal

* Forgot 'break;' for covecube layer

* Tweak Viterbi files now that I have hands on

* Add secrets to Ergodox

* RGB tweaks to Viterbi

* Viterbi RGB layout tweeks

* Minor tweaks

* Add One Shot Mod tap toggle

* Add Faux Clicky to Viterbi, and disable controller's LEDs

* Minor tweaks

* Move D3 keycode defines into userspace

* Updated Userspace Readme
 		2018-01-01 17:21:01 -05:00
..
keymaps Clean up and tweaks of drashna keymaps and userspace (#2200) 2018-01-01 17:21:01 -05:00
config.h Updates bootloader settings, adds file size check (#2029) 2017-11-27 23:08:21 -05:00
readme.md updated drashna's keymaps (#1769) 2017-09-29 11:52:37 -10:00
rules.mk Updates bootloader settings, adds file size check (#2029) 2017-11-27 23:08:21 -05:00
woodpad.c updated drashna's keymaps (#1769) 2017-09-29 11:52:37 -10:00
woodpad.h updated drashna's keymaps (#1769) 2017-09-29 11:52:37 -10:00

readme.md

woodpad 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/woodpad 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.