Skip to content
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

Conversation

just-another-jxliu
Copy link
Contributor

@just-another-jxliu just-another-jxliu commented Aug 19, 2019

Description

New keyboards:

  • Rocketeer support
  • 1800-layout SHIFT prototype support, will need to change in the future to support the layout change to compact 1800.

For CTRL, ALT, Rocketeer, SHIFT:

  • LED matrix: new toggle to only enable every other edge LED and new dedicated edge brightness controls.
  • LED matrix: new pattern directions up/down and circular.
  • Debounce behavior change.
  • Increase soft boot minimum hold time from 0.5 seconds to 2 seconds
  • Remove U_T_AUTO/usb_extra_manual
  • Modified power management
  • Under-the-hood changes to accommodate hardware differences between CTRL, ALT, Rocketeer, and SHIFT.

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

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

Checklist

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

* 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
@pschmuckal
Copy link

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.

@drashna drashna requested a review from a team January 18, 2020 06:53
@drashna
Copy link
Member

drashna commented Jan 18, 2020

@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.
Also, ideally, splitting up the PRs so that core changes aren't included with keyboard changes, helps us out a lot.
https://docs.qmk.fm/#/contributing?id=general-guidelines

@drashna drashna requested a review from a team January 19, 2020 21:15
@pschmuckal
Copy link

pschmuckal commented Jan 22, 2020

@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.

@stale
Copy link

stale bot commented Mar 7, 2020

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

@stale stale bot removed the awaiting changes label Mar 8, 2020
@drashna drashna added the breaking_change Changes that need to wait for a version increment label Mar 10, 2020
@drashna
Copy link
Member

drashna commented Mar 24, 2020

Some merge conflicts here

@fauxpark fauxpark mentioned this pull request Apr 19, 2020
13 tasks
@tzarc tzarc added on hold and removed in progress labels Jul 16, 2020
@drashna drashna self-requested a review September 15, 2020 05:42
@drashna
Copy link
Member

drashna commented Sep 15, 2020

@just-another-jxliu @pschmuckal was there any plans to update this and resolve the merge conflicts here?

@tzarc
Copy link
Member

tzarc commented Nov 10, 2020

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!

@tzarc tzarc removed the on hold label Nov 10, 2020
@tzarc
Copy link
Member

tzarc commented Dec 20, 2020

Apparently the breaking change label is preventing stalebot from closing this PR.
Please refer to #11119. Closing.

@tzarc tzarc closed this Dec 20, 2020
xwu added a commit to xwu/qmk_firmware that referenced this pull request Jul 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking_change Changes that need to wait for a version increment core enhancement keyboard keymap
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for Massdrop x Zslane Mercury Rocketeer
9 participants