-
-
Notifications
You must be signed in to change notification settings - Fork 39.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rocketeer support and updates to Drop/Massdrop keyboards #6568
Rocketeer support and updates to Drop/Massdrop keyboards #6568
Conversation
* CTRL (arm_atsam) support user-defined LED instructions * ok, layer matching works now * Bitwise LED ID to reduce number of instructions (performance) * Use 32-bit ints to be more compatible with generation in JS * TYpo
Updates to get the package compiling and working for the most part Bug with reactive lighting for QMK code and keeping caps/num lock lit when on
- In config.h of each, added '#define BOOTKEY_HOLD_MS 2000' to define hold time required to active Boot key (was 500ms hardcode) - Updated all active keymap.c files to use this define - Added line in quantum.c in MAGIC_TOGGLE_NKRO case to clear_keyboard() before toggling nkro state to fix stuck key issues when switching NKRO.
* Clean-up for merge to main QMK repo * Update info.json/readme.md * More fixes, clean-up * Spacing for readme.md
…iu/rocketeer-support-and-updates
What do you need from us (Drop) to get this PR closed? We realize it is not ideal due to # of mods, but these changes were done almost a yr ago by a contractor no longer involved and are needed to support our shipping products. Also heads up - there are a number of additional changes coming down the pipe to support other new products coming very soon. |
@pschmuckal more time. It's a large change, touching a BUNCH of files. What would help in the future is smaller, more incremental changes, as they're easier to review and get merged in, in a timely manner. |
@drashna Understood, and apologize once again about the excessive number of mods here. Note that our HW design has changed significantly for newer products which is one reason why so many files were touched, as well as adding additional 'config' files into the keyboards dirs. Not sure I could split up this PR easily and still be buildable. |
Thank you for your contribution! |
Some merge conflicts here |
@just-another-jxliu @pschmuckal was there any plans to update this and resolve the merge conflicts here? |
This PR hasn't seen progress in quite some time. As such, I'm removing the labels that prevent stalebot from auto-closing this PR. You're free to add commits or comments to keep it alive, but for now there's no reason to keep it open if it's going to sit here inactive. The requirements for PRs have changed since it was raised, so if you'd like to continue the process of getting this into QMK, please refer to the PR Checklist and make the required changes in your next batch of commits. Feel free to reach out to any of the collaborators if you're unsure of things, or even better, ping one of the collaborators on Discord and we can take it from there. Thanks! |
Apparently the breaking change label is preventing stalebot from closing this PR. |
Description
New keyboards:
For CTRL, ALT, Rocketeer, SHIFT:
U_T_AUTO
/usb_extra_manual
Keymap issues:
massdrop/ctrl:responsive_pattern
compiles, but LEDs are not functional because the keymap uses outdated LED functions. Same issue on master. Will fix in a future PR.Types of Changes
Issues Fixed or Closed by This PR
Checklist