Go to file
2018-01-28 12:23:28 -05:00
.vscode
docs Clarify the format for layout names 2018-01-19 11:58:19 -08:00
drivers
keyboards Add helix keyboard (#2308) 2018-01-28 12:14:12 -05:00
layouts
lib
quantum Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
tests
tmk_core Revert back to normal sleeping wait behaviour for STM32 2018-01-21 01:10:16 -08:00
users Update to drashna keymaps (#2281) 2018-01-17 11:28:23 -08:00
util update sed to work on mac 2018-01-28 12:23:28 -05:00
.clang_complete
.editorconfig
.gitattributes
.gitignore
.gitmodules
.travis.yml
autocomplete.sh
book.json
bootloader.mk
build_full_test.mk
build_keyboard.mk
build_layout.mk
build_test.mk
CODE_OF_CONDUCT.md
common_features.mk Backlighting for JJ40 and underglow initialisation code (#2260) 2018-01-18 16:02:32 -05:00
common.mk
Dockerfile
LICENSE
license_GPLv2.md
license_GPLv3.md
license_Modified_BSD.md
Makefile
message.mk Reset color after submodule warning message 2018-01-12 13:25:05 -05:00
readme.md
secrets.tar.enc
shell.nix
testlist.mk
Vagrantfile

Quantum Mechanical Keyboard Firmware

Current Version Build Status Gitter Docs Status GitHub contributors GitHub forks

This is a keyboard firmware based on the tmk_keyboard firmware with some useful features for Atmel AVR and ARM controllers, and more specifically, the OLKB product line, the ErgoDox EZ keyboard, and the Clueboard product line.

Official website

http://qmk.fm is the official website of QMK, where you can find links to this page, the documentation, and the keyboards supported by QMK.

Supported Keyboards

The project also includes community support for lots of other keyboards.

Maintainers

QMK is developed and maintained by Jack Humbert of OLKB with contributions from the community, and of course, Hasu. The OLKB product firmwares are maintained by Jack Humbert, the Ergodox EZ by Erez Zukerman, and the Clueboard by Zach White.

Documentation

https://docs.qmk.fm is hosted on Gitbook and GitHub (they are synced). You can request changes by making a fork and pull request, or by clicking the "suggest an edit" link on any page of the Docs.