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

Add the Abats Keyboard Club Nayeon #1423

Merged
merged 3 commits into from
Sep 27, 2022
Merged

Add the Abats Keyboard Club Nayeon #1423

merged 3 commits into from
Sep 27, 2022

Conversation

ramonimbao
Copy link
Contributor

Description

Adds the Abats Keyboard Club Nayeon keyboard.

QMK Pull Request

qmk/qmk_firmware#16659

Checklist

  • The VIA support for this keyboard is in QMK master already (MANDATORY)
  • The VIA definition follows the guide here: https://caniusevia.com/docs/layouts
  • I have tested this keyboard definition using VIA's "Design" tab.
  • I have tested this keyboard definition with firmware on a device.
  • I have assigned alpha keys and modifier keys with the correct colors.
  • The Vendor ID is not 0xFEED

@Xelus22 Xelus22 added bug Something isn't working invalid This doesn't seem right and removed bug Something isn't working labels Sep 26, 2022
@ramonimbao
Copy link
Contributor Author

Hey @Xelus22, how would I go about with this? The conflicting keyboard is the Keygem KG60 (#1303) but checking the PR for it, it hasn't been merged to QMK yet (qmk/qmk_firmware#17565).

@Xelus22
Copy link
Collaborator

Xelus22 commented Sep 27, 2022

The automatic build says it is failing. So please fix any errors.

@ramonimbao
Copy link
Contributor Author

The error is that the Keygem K60 conflicts with the Nayeon, but the Keygem K60 isn't merged yet with QMK despite being merged with VIA.

@wilba
Copy link
Contributor

wilba commented Sep 27, 2022

I did merge the Keygem boards into VIA before they were in QMK master.

That did not throw an error because the Nayeon VID/PID was not in VIA yet, so there was no conflict.

This is the first time we've had to deal with such a conflict, and it's a bit complicated.

@mrnoisytiger could have checked the VID/PID was unique (in QMK) before their PR to QMK and VIA

However, it is using ASCII codes "KG" for the VID (i.e. Keygem) and there's no obvious reason why "Abats Keyboard Club Nayeon" would be using "KG".

@ramonimbao @mrnoisytiger Can you give more information about this, and have a discussion here please?

I'd like a solution that is the least inconvenient to the people owning the PCBs, and least disruptive to both of you.

@ramonimbao
Copy link
Contributor Author

The 4B47 is just very loosely based on Abats. I am alright with changing the VID/PID in QMK and then updating it here. I have some VIAL firmware prepared for the Nayeon since the boards use RP2040 and were made before the latest breaking change.

@Xelus22
Copy link
Collaborator

Xelus22 commented Sep 27, 2022

I guess you could just use ABA7?

@mrnoisytiger
Copy link
Contributor

I chose 4B47 specifically because of a client request to use the KG hexcodes for KeyGem. Unfortunately we already have many boards produced with this firmware and they are already in market (with multiple variants too, basically copying all the DZ__ variants). I think like Xelus suggested to use ABA7 would be the least breaking and would probably align with Abats better?

@ramonimbao
Copy link
Contributor Author

Alright, will go with ABA7. Thanks.

@ramonimbao
Copy link
Contributor Author

Well that was quick. The new VID has been merged into QMK. Thanks everyone!

@wilba
Copy link
Contributor

wilba commented Sep 27, 2022

ggwp

@wilba wilba merged commit 9ff7b7b into the-via:master Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants