logo

qmk_firmware

custom branch of QMK firmware git clone https://anongit.hacktivis.me/git/qmk_firmware.git

faq_general.md (3590B)

    

  1. # Frequently Asked Questions
  3. ## What is QMK?
  5. [QMK](https://github.com/qmk), short for Quantum Mechanical Keyboard, is a group of people building tools for custom keyboards. We started with the [QMK firmware](https://github.com/qmk/qmk_firmware), a heavily modified fork of [TMK](https://github.com/tmk/tmk_keyboard).
  7. ## I don't know where to start!
  9. If this is the case, then you should start with our [Newbs Guide](newbs). There is a lot of great info there, and that should cover everything you need to get started.
  11. If that's an issue, hop onto the [QMK Configurator](https://config.qmk.fm), as that will handle a majority of what you need there.
  13. ## How can I flash the firmware I built?
  15. First, head to the [Compiling/Flashing FAQ Page](faq_build). There is a good deal of info there, and you'll find a bunch of solutions to common issues there.
  17. ## What if I have an issue that isn't covered here?
  19. Okay, that's fine. Then please check the [open issues in our GitHub](https://github.com/qmk/qmk_firmware/issues) to see if somebody is experiencing the same thing (make sure it's not just similar, but actually the same).
  21. If you can't find anything, then please open a [new issue](https://github.com/qmk/qmk_firmware/issues/new)!
  23. ## What if I found a bug?
  25. Then please open an [issue](https://github.com/qmk/qmk_firmware/issues/new), and if you know how to fix it, open up a Pull Request on GitHub with the fix.
  27. ## But `git` and `GitHub` are intimidating!
  29. Don't worry, we have some pretty nice [Guidelines](newbs_git_best_practices) on how to start using `git` and GitHub to make things easier to develop.
  31. Additionally, you can find additional `git` and GitHub related links [here](newbs_learn_more_resources).
  33. ## I have a Keyboard that I want to add support for
  35. Awesome! Open up a Pull Request for it. We'll review the code, and merge it!
  37. ### What if I want to brand it with `QMK`?
  39. That's amazing! We would love to assist you with that!
  41. In fact, we have a [whole page](https://qmk.fm/powered/) dedicated to adding QMK Branding to your page and keyboard. This covers pretty much everything you need (knowledge and images) to officially support QMK.
  43. If you have any questions about this, open an issue or head to [Discord](https://discord.gg/qmk).
  45. ## What Differences Are There Between QMK and TMK?
  47. TMK was originally designed and implemented by [Jun Wako](https://github.com/tmk). QMK started as [Jack Humbert](https://github.com/jackhumbert)'s fork of TMK for the Planck. After a while Jack's fork had diverged quite a bit from TMK, and in 2015 Jack decided to rename his fork to QMK.
  49. From a technical standpoint QMK builds upon TMK by adding several new features. Most notably QMK has expanded the number of available keycodes and uses these to implement advanced features like `S()`, `LCTL()`, and `MO()`. You can see a complete list of these keycodes in [Keycodes](keycodes).
  51. From a project and community management standpoint TMK maintains all the officially supported keyboards by himself, with a bit of community support. Separate community maintained forks exist or can be created for other keyboards. Only a few keymaps are provided by default, so users typically don't share keymaps with each other. QMK encourages sharing of both keyboards and keymaps through a centrally managed repository, accepting all pull requests that follow the quality standards. These are mostly community maintained, but the QMK team also helps when necessary.
  53. Both approaches have their merits and their drawbacks, and code flows freely between TMK and QMK when it makes sense.