qmk_firmware
QMK, forked for ZSA's Oryx Configurator (to safeguard stability) (by zsa)
qmk_firmware
Open-source keyboard firmware for Atmel AVR and Arm USB families (by qmk)
Our great sponsors
qmk_firmware | qmk_firmware | |
---|---|---|
17 | 1,587 | |
270 | 17,079 | |
5.6% | 2.1% | |
0.0 | 10.0 | |
about 1 month ago | 5 days ago | |
C | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
qmk_firmware
Posts with mentions or reviews of qmk_firmware.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-06.
-
Corne and planck
Hey guys more than a qmk question I have a GitHub question, I have a corne, lilf58 and a zsa plank keyboards, I use a variation of Dvorak which is totally custom so I mantain my own branch ir order to have the same layout across my keyboards to have the same experience when I switch between them but the zsa branch is a fork from the qmk (https://github.com/zsa/qmk_firmware/fork) but git don't allow me to do another fork. I would like to have my changes pushed in both projects what I currently do is have a fork for my corn and lily and in my fork I put my changes, and for the zsa fork I just clone it in my machine but I can't push anything to have a backup I would only like to change between branches to have access to my other keybs, sorry for the long post if any one else has this issue, how do you solve it?
- How is compiling ZSA supposed to work?
-
What QMK version does ORYX use?
They have their own fork. https://github.com/zsa/qmk_firmware
-
Is it possible for the PC to detect Raise/Lower with QMK?
ZSA's oryx training does that, but it needs web-usb iirc. As they use a QMK fork, someone with more experience may be able to reproduce that with their own layout and a basic that handles the "monitoring traffic".
- Firmware v22.0
-
Moonlander: how to have a game layer that turns off all lag-producing settings??
Head over to ZSA's source on Github, scroll down to the building section. Take a note of the command it mentions there, but otherwise follow along with the instructions in that "Newbs guide from QMK."
- Planck EZ sound changed on firmware v21
-
Auto shift works properly everywhere but vim
ZSA’s QMK fork doesn’t have a bug tracker, and I’m not sure whether Oryx has one. But Drashna did open an Auto Shift-related pull request a couple of days ago!
-
Has the latest Moonlander firmware (v21.0) changed key timings?
You can see a full list here: https://github.com/zsa/qmk_firmware/wiki/Changelog
-
Ergodox custom animation
Apologies if there is a better way to post code How I did this: * Forked the zsa repo for ergodox * https://github.com/zsa/qmk_firmware * Followed the newbie guide to setup QMK environment * https://docs.qmk.fm/#/newbs * Went to my current layout in oryz and selected Download Source (Glow) * Created a directory for my code in the forked repo * qmk_firmware > keyboards > ergodox_ez > glow > keymaps > shadowra88it * Copied the contents of my source folder to that directory * config.h , keymap.c, rules.mk * I disabled all the animations I didn't want so that I didn't have to cycle so much in config.h and defined using keypresses * keymaps.c I left alone. * rules.mk I added RGB_MATRIX_CUSTOM_USER = yes to the end of the file. * Then all the magic happens in the newly created rgb_matrix_user.inc
qmk_firmware
Posts with mentions or reviews of qmk_firmware.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2024-01-14.
- Lkbm: LED-Key BitMasks to Control the Ploopy Nano Trackball
-
QMK and Keyboards
Separate wireless controller, see the glue code at [0]
[0]: https://github.com/qmk/qmk_firmware/compare/master...nuphy-s...
-
Debugging a Failing Hotkey
If you have a keyboard that runs QMK firmware[0] with the VIA[1] feature enabled[2], then there is a convenient testing app available from the same place you customize your keys [3].
[0] https://qmk.fm/
- How to make 2 or more layers become default ON with key
-
Just setting up my first corne layout. It will take a while for me to get used to this wow... It's taking so long to type. Attached is my layout, and I mainly use c# on visual studio. Any concerns/advice/suggestions are welcome. It will take a while for me to reply on this thing though.. haha..
I made a layout that I'm happy with. Spanish is my native language, so it has characters like the accents and 'ñ', but it's meant to be used for programming as well. Visual Studio uses a lot of Ctrl and Ctrl + Shift shortcuts, so I left them in the same place as the default Corne layout so I can press them both with my pinkie finger. Perhaps some of the ideas are useful to you.
-
Adafruit Feather RP2040 with USB Type A Host as a QMK converter board?
Also, it would be possible to do this for the RP2040. However, it needs some work to get working. but for example: https://github.com/qmk/qmk_firmware/pull/20999
-
If anyone knows of a good tutorial on how to make this tft display useful on a board controlled by an rp2040 and flashed with qmk configurator, I would be most grateful if you could point me in that direction. Gracias!
Ok, it's an ST7735, not too different from the ST7789. You should be able to get running by looking at their files in the QMK repo and going from there. You should also check their resources page.
- Keyboard missing from QMK MSYS.
-
Bongocat or other cool oled animation for Lily or Sofle
UPDATE: after fluffing around a little bit, I have manged to fix this code: https://github.com/qmk/qmk_firmware/blob/master/keyboards/lily58/keymaps/bongocat_wpm_responsive/keymap.c and flash it successfully - it seems not to be working correctly as the cat is only hanging there and does not respond to the wmp count. If anybody spots anything wrong in the code please let me know!(C is not my language but I am a programmer, I am gonna get at it again over the weekend if I have time left)
-
Between the Seniply and Callum layouts, what did you end up choosing and why?
For Seniply I've found this implementation for a_dux keyboard: QMK
What are some alternatives?
When comparing qmk_firmware and qmk_firmware you can also consider the following projects:
qmk_firmware - See the "forkreadme" branch or the following link for a description of branches maintained in this fork.
zmk - ZMK Firmware Repository
qmk_configurator - The QMK Configurator
kmk_firmware - Clackety Keyboards Powered by Python
layoverlay
vial-qmk - QMK fork with Vial-specific features.
emgo - Emgo: Bare metal Go (language for programming embedded systems)
kmonad - An advanced keyboard manager
qmk_firmware - Moonlander firmware
pico-examples
qmk_firmware - keyboard controller firmware for Atmel AVR USB family
zmk-config - ZMK Configuration
qmk_firmware vs qmk_firmware
qmk_firmware vs zmk
qmk_firmware vs qmk_configurator
qmk_firmware vs kmk_firmware
qmk_firmware vs layoverlay
qmk_firmware vs vial-qmk
qmk_firmware vs emgo
qmk_firmware vs kmonad
qmk_firmware vs qmk_firmware
qmk_firmware vs pico-examples
qmk_firmware vs qmk_firmware
qmk_firmware vs zmk-config