-
Notifications
You must be signed in to change notification settings - Fork 44
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
keyboards: Add support for Sofle Choc #6
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Squash ok with me. How do plan to get this into PR? Force push the choc2 branch?
Yes. But before that somebody needs to test it on a physical device. |
I can test it tonight. |
The warnings during flashing seem unrelated. I'll take a look at the display, did it work with the original PR? Are keypresses, LEDs working? |
Regular keypresses without modifier keys are working normal. Shift modifier works too. It seems the layer shifting modifiers don't work as shown on in the default layout depicted in the build guide. E.g. when pressing any layer modifier in combination with " I can only see the default red pulsing. Due to the disfunctional layer modifiers I can't switch the animation and/or LED color. |
The layers being gone is intentional, as the maintainers requested a simpler keymap by default. |
Do you really think this is what Drashna means with "pristine/simple"? Even the corne keyboard has layers in its default keymap. And the default map has Drashna in its copyright message. But to get this board merged I would be ok with that, but then I would appreciate it if you move the previous default map to something like "old default", "brians default" or "creators default". What good is it having a RGB board if you can't change anything RBG related? |
If one can't change the animation you should then also comment out all other animations except for the one used in |
This was my impression, yes.
I would prefer to keep this out of the initial PR. Let's focus on the minimal amount of stuff to make it useful and get it merged. The original layout is a nice example but it's much easier to add it after the initial merge.
I'll delete them completely for the first merge. |
Agreed.
Do that and I'll approve. |
And did you look into the the crippeled OLED display? |
I didn't have time yet to look at the OLED. Will do so later. |
What upstreaming PR do mean? I checked out your PR without any modifications, compiled and flashed it to my Sofle Choc. |
@duese Thanks for testing! Care to try again? |
Bumps [tj-actions/changed-files](https://github.com/tj-actions/changed-files) from 37 to 38. - [Release notes](https://github.com/tj-actions/changed-files/releases) - [Changelog](https://github.com/tj-actions/changed-files/blob/main/HISTORY.md) - [Commits](tj-actions/changed-files@v37...v38) --- updated-dependencies: - dependency-name: tj-actions/changed-files dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
GCC 13 needs the same workaround as GCC 12. To avoid having to maintain an ever-growing list of broken versions apply the workaround wherever it can be used. If at some point a fixed version of GCC is released the workaround can be disabled for those fixed versions. See qmk#17064
* Move RGBLight animations to data driven, 0-9 * Move RGBLight animations to data driven, A * Move RGBLight animations to data driven, B * Move RGBLight animations to data driven, C * Move RGBLight animations to data driven, D * Move RGBLight animations to data driven, E * Move RGBLight animations to data driven, F * Move RGBLight animations to data driven, G * Move RGBLight animations to data driven, H * Move RGBLight animations to data driven, handwired * Move RGBLight animations to data driven, I * Move RGBLight animations to data driven, J * Move RGBLight animations to data driven, K * Move RGBLight animations to data driven, L * Move RGBLight animations to data driven, M * Move RGBLight animations to data driven, N * Move RGBLight animations to data driven, O * Move RGBLight animations to data driven, P * Move RGBLight animations to data driven, Q * Move RGBLight animations to data driven, R * Move RGBLight animations to data driven, S * Move RGBLight animations to data driven, T * Move RGBLight animations to data driven, U * Move RGBLight animations to data driven, V * Move RGBLight animations to data driven, W * Move RGBLight animations to data driven, X * Move RGBLight animations to data driven, Y * Move RGBLight animations to data driven, Z * Fix incorrect placement * Fix build failures and mismatches
* Rework info.json reference * Apply suggestions from code review Co-authored-by: Sergey Vlasov <[email protected]> * Update backlight.pins description * Add rgblight.driver and lowercase other driver names * Remove `split.main` and `split.matrix_grid` for now as they are not working yet --------- Co-authored-by: Sergey Vlasov <[email protected]>
* Partially revert qmk#19780 * Finish * Get teensy 3.5/3.6 board files too * fix lint issue * Revert "[Bug] Restore usb suspend wakeup delay (qmk#21676)" This reverts commit e8e989f. * Apply suggestions from code review Co-authored-by: Joel Challis <[email protected]> --------- Co-authored-by: Joel Challis <[email protected]>
Co-authored-by: James Young <[email protected]> Co-authored-by: Ryan <[email protected]> Co-authored-by: honorless <[email protected]>
Co-developed-by: Brian Low <[email protected]> Co-developed-by: duese <[email protected]>
This PR is to review and test my changes for the Sofle Choc upstreaming process.
@brianlow @duese are you fine with me squashing all your work into this commit together?
There is authorship attribution in the commit message.