qmk_firmware/docs
yiancar a7df902734 Addition of hard brigtness limit for RGB_Matrix (#3299)
* Addition of hard brigtness limit for RGB_Matrix

- Added a define "RGB_MATRIX_MAXIMUM_BRIGHTNESS" to enable hard limiting the maximum brightness for rgb_matrix
- Used the above define to limit the maximum brigthness of HS60 for better stability

* Added docs for new rgb_matrix define

* Addition of check for maximum brightness
2018-07-03 12:52:04 -04:00
..
gitbook/images
.nojekyll
CNAME Create CNAME 2018-05-21 16:29:37 -04:00
README.md
_sidebar.md
_summary.md
becoming_a_qmk_collaborator.md
compatible_microcontrollers.md
config_options.md
contributing.md
custom_quantum_functions.md
documentation_best_practices.md
documentation_templates.md
eclipse.md
faq.md
faq_build.md
faq_debug.md
faq_general.md
faq_keymap.md
feature_advanced_keycodes.md Fix up info boxes. 2018-05-07 22:46:26 -07:00
feature_audio.md
feature_auto_shift.md
feature_backlight.md
feature_bluetooth.md
feature_bootmagic.md Fix link to command page 2018-04-15 11:53:31 -04:00
feature_command.md
feature_dynamic_macros.md
feature_grave_esc.md
feature_key_lock.md
feature_layouts.md Clarify the format for layout names 2018-01-19 11:58:19 -08:00
feature_leader_key.md
feature_macros.md
feature_mouse_keys.md
feature_pointing_device.md
feature_ps2_mouse.md
feature_rgb_matrix.md Addition of hard brigtness limit for RGB_Matrix (#3299) 2018-07-03 12:52:04 -04:00
feature_rgblight.md Add rgblight mode 35 (R,G,B test mode) (#3114) 2018-06-04 08:10:39 -07:00
feature_space_cadet.md
feature_space_shift_cadet.md
feature_stenography.md Improve state/chord handling and clean up namespace 2018-04-07 17:12:44 -04:00
feature_swap_hands.md
feature_tap_dance.md
feature_terminal.md
feature_thermal_printer.md
feature_unicode.md
feature_userspace.md
features.md
flashing.md
fuse.txt
getting_started_build_tools.md
getting_started_getting_help.md
getting_started_github.md
getting_started_introduction.md
getting_started_make_guide.md
getting_started_vagrant.md
hand_wire.md
hardware.md Fix some of the more obvious typos 2017-12-09 10:46:11 -05:00
hardware_avr.md
hardware_drivers.md
hardware_keyboard_guidelines.md
how_keyboards_work.md
index.html
internals_defines.md
internals_input_callback_reg.md
internals_midi_device.md
internals_midi_device_setup_process.md
internals_midi_util.md
internals_send_functions.md
internals_sysex_tools.md
isp_flashing_guide.md
keycode.txt
keycodes.md Clean up SEND_STRING keycodes and add media keys (#3214) 2018-06-28 08:55:04 -04:00
keycodes_basic.md
keycodes_us_ansi_shifted.md
keymap.md
newbs.md
newbs_building_firmware.md
newbs_flashing.md
newbs_getting_started.md
newbs_testing_debugging.md
porting_your_keyboard_to_qmk_(arm_and_other_chibios_cpus).md
power.txt
qmk.css
quantum_keycodes.md
redirects.json
reference_glossary.md Disable the glossary linking to fix #2498 (#2499) 2018-03-08 10:31:08 -08:00
sidebar.css
sw.js Fix up info boxes. 2018-05-07 22:46:26 -07:00
understanding_qmk.md
unit_testing.md
usb_nkro.txt

README.md

Quantum Mechanical Keyboard Firmware

Current Version Build Status Discord Docs Status GitHub contributors GitHub forks

What is QMK Firmware?

QMK (Quantum Mechanical Keyboard) is an open source community that maintains QMK Firmware, QMK Toolbox, qmk.fm, and these docs. QMK Firmware is a keyboard firmware based on the tmk_keyboard with some useful features for Atmel AVR controllers, and more specifically, the OLKB product line, the ErgoDox EZ keyboard, and the Clueboard product line. It has also been ported to ARM chips using ChibiOS. You can use it to power your own hand-wired or custom keyboard PCB.

How to Get It

If you plan on contributing a keymap, keyboard, or features to QMK, the easiest thing to do is fork the repo through Github, and clone your repo locally to make your changes, push them, then open a Pull Request from your fork.

Otherwise, you can either download it directly (zip, tar), or clone it via git (git@github.com:qmk/qmk_firmware.git), or https (https://github.com/qmk/qmk_firmware.git).

How to Compile

Before you are able to compile, you'll need to install an environment for AVR or/and ARM development. Once that is complete, you'll use the make command to build a keyboard and keymap with the following notation:

make planck/rev4:default

This would build the rev4 revision of the planck with the default keymap. Not all keyboards have revisions (also called subprojects or folders), in which case, it can be omitted:

make preonic:default

How to Customize

QMK has lots of features to explore, and a good deal of reference documentation to dig through. Most features are taken advantage of by modifying your keymap, and changing the keycodes.