gmmk: support VIA

[gloryhzw]

Description

1. Support VIA keymap
2. Optimize rev2 I2C

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: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• 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).

[DaoWen]

@gloryhzw - Does VIA software work for you after flashing the "via" firmware you merged here? I'm just curious because I tried flashing it to my GMMK Full Rev3, and VIA refused to detect my device.

Regardless, the updates to the keymaps and other changes you made were very helpful to me. I don't mind running qmk locally, so not having VIA isn't a big deal. After a few iterations and using your patch as an example, I was finally able to get my GMMK configured with the hotkey bindings and RGB_MATRIX_SOLID_REACTIVE LED scheme that I wanted.

TL;DR — Thanks for contributing this patch!

EDIT: Talked to @gloryhzw on discord, and it turns out that I just needed to load the keymap json into VIA, and then it picked it up my device right away. 🤦‍♂️

[gloryhzw]

Have a nice time with qmk:)

…

On Dec 15, 2021, at 3:00 AM, Nick Vrvilo ***@***.***> wrote:  @gloryhzw - Does VIA software work for you after flashing the "via" firmware you merged here? I'm just curious because I tried flashing it to my GMMK Full Rev3, and VIA refused to detect my device. Regardless, the updates to the keymaps and other changes you made were very helpful to me. I don't mind running qmk locally, so not having VIA isn't a big deal. After a few iterations and using your patch as an example, I was finally able to get my GMMK configured with the RGB_MATRIX_SOLID_REACTIVE scheme that I wanted. TL;DR — Thanks for contributing this patch! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[guilleortas]

I'm getting a segfault error when trying to build any of the variants listed in the readme of the GMMK 1 full-size.
I'm using a clean install of QMK MSYS, I can't tell what's going on and I'd really like to build this firmware

[gloryhzw]

Try to use the latest qmk msys 1.7.1

[guilleortas]

I'm sorry for my blunt message, I'd like to really thank the SonixQMK project for the amazing work you're doing, it's such a powerful resource.
I was already using v1.7.1, and I have tried a clean install on a different computer but the problem is still there. Does it compile for you?

[guilleortas]

To update on this matter, removing a few folders you don't need from the keyboards directory seems to do the trick: This is connected to stack size, see this issue for more insight.

[gloryhzw]

No issue for 1.7.1 here. You can go sonixqmk discord for help: https://discord.com/channels/805578807477534750/805578807477534754 guilleortas ***@***.***> 於 2022年8月19日 週五 下午2:00寫道：

…

I'm sorry for my blunt message, I'd like to really thank the SonixQMK project for the amazing work you're doing, it's such a powerful resource. I was already using v1.7.1, and I have tried a clean install on a different computer but the problem is still there. Does it compile for you? — Reply to this email directly, view it on GitHub <#147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEBFGTT6GQMFGNZYRTHSSOTVZ4PJDANCNFSM5HXWGHYQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>