-
-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Add gBoards GergoPlex firmware #10406
Conversation
Co-Authored-By: Drashna Jaelre <[email protected]>
Co-authored-by: Drashna Jaelre <[email protected]>
Via doesn't support chords/combos, and this makes the keymap on such a small keyboard quite uncomfortable and incomplete.
|
||
// unused pins - C7, D4, D5, D7, E6 | ||
// set as input with internal pull-up enabled | ||
DDRB &= ~(1 << 0 | 1 << 4 | 1 << 5 | 1 << 6 | 1 << 7); |
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.
I intend to replace this according to this comment:
We rather use the GPIO control functions: https://docs.qmk.fm/#/internals_gpio_control?id=functions
Hi @pirj! I just received my Gergoplex and I'm looking to start personalizing my keymap. I don't see the Gergoplex layout in master yet, should I create a fork off of yours to start my modifications? I also see a couple other PRs opened by Germ for this board, not sure which one is the best base to work off of. |
Hey @baylessj . Got ahead, check out this branch and test it. It's currently driving my GergoPlex with no issues. It's a cleanup and minor refactoring of the original pull request. I plan to work on this even further, but that shouldn't prevent you from hacking in your layout - |
Thanks for working on this @pirj, currently typing on my fork of your fork. Took a bit to get used to the organization of the key combo code when modifying that but everything else was smooth sailing with making my keymap. |
FWIW I also have been running this branch (with @drashna's suggested changes on the layout definition applied) with my keymap for a week or so and haven't had any issues. |
Here is a commit to add That branch can be used to build miryoku for the gergoplex by merging in the miryoku development branch. |
I can confirm merging manna-harbour@bba7a50 and manna-harbour:miryoku into pirj:prettify-gergoplex builds and is functional on my GergoPlex with the command |
Thank you for your contribution! |
What else is left todo here? sorry, new around here and have a gergoplex =) |
Same here: I recently got a Gergoplex as well and have been using this PR, which thus far works great. It would be nice to see this merged into QMK at some point 😄 |
Sorry, it is taking me longer to get back to this.
|
Any progress on this pull request? I'd love to help out in whatever way I can, but my knowledge of QMK internals is pretty much non-existing. If anything needs testing, let me know 😄 |
Thank you for your contribution! |
This really should still get merged in... @pirj are you able to get back to those action items you listed in your comment above? Or would you prefer if someone else takes over the finishing touches on the PR? |
@baylessj Not yet. There are a few cosmetic things that need to be done. I appreciate if someone takes this over. Or I can do it, but I'd love to take a chance with reusing the code from ergodox, and this will take longer than just cosmetic changes. |
PR updated. @drashna, please have a look. What has been done:
What has NOT been done:
@germ do you mind having a look, and test it out, too? |
// unused pins - C7, D4, D5, D7, E6 | ||
// set as input with internal pull-up enabled | ||
DDRB &= ~(1 << 0 | 1 << 4 | 1 << 5 | 1 << 6 | 1 << 7); | ||
PORTB |= (1 << 0 | 1 << 4 | 1 << 5 | 1 << 6 | 1 << 7); |
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.
I don't understand what's going on, it's updated in my branch that is linked to this PR https://github.com/pirj/qmk_firmware/blob/prettify-gergoplex/keyboards/gboards/gergoplex/gergoplex.c, but not here.
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.
GitHub probably doesn't update closed PRs.
This PR doesn't seem to be updated with my branch updates for some reason. |
cloned pirj's branch, built, flashed and am running this latest update on my gergoplex, things seem OK - will update if something seems broken as I use the keyboard today |
Description
Add firmware for gBoards GergoPlex.
This PR differ from the original GergoPlex pull request:
master
(in hopes forbreaking changes
to be removed, since it doesn't affect any existing firmware, but introduces a new one)LAYOUT_kc
instead ofLAYOUT_split_3x5_3
, asked a question how to benefit from both)All @germ's original commits are left intact.
Not done
According to
custom_matrix.md
:And MCP23018, I/O port expander, is used for the left half of the split keyboard.
feature_split_keyboard.md
suggests:And GergoPlex is only using one AVR, and MCP is used for the other half (just like ErgoDox EZ, torn, spiderisland/split78, moonlander, ymdk/sp64, wheatfield/split75, sx60, net_type_a, hotdox, handwired/ferris, ergotaco, other gBoards keyboards, and a fair number of keyboards using
PORT_EXPANDER_ADDRESS
in their firmwares).I hope to get rid of at least a part of the custom matrix code using
MATRIX_ROW_PINS
,MATRIX_COL_PINS
,DIODE_DIRECTION
.Also to only keep a fraction of MCP23018 code with
SPLIT_KEYBOARD=true
andSPLIT_TRANSPORT=custom
,SOFT_SERIAL_PIN
,USE_I2C
etc.Will do this in a follow-up, since it's not too straightforward.
Types of Changes
Issues Fixed or Closed by This PR
Checklist