-
-
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 jels60v2 support #21337
add jels60v2 support #21337
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.
keyboard updates and refactors (eg. to data driven) must go through develop to reduce master -> develop merge conflicts
This would include adding to data/mappings/keyboard_aliases.hjson
for jels/jels60
to jels/jels60/v1
compatibility.
@zvecr would I be able to add a temporary keyboard (i.e jels/jels60v2) to master (so that I can change VIA) and then put in a pr for refactoring targeted towards develop? |
Co-authored-by: Joel Challis <git@zvecr.com>
Co-authored-by: Joel Challis <git@zvecr.com>
IIRC, via doesn't actually provide firmware images. The collection that they have is very much out of date, I believe. So, really, it's up to you to provide them. So compiling from source means that you should be able to compile from develop. So shouldn't be an issue. |
Co-authored-by: Joel Challis <git@zvecr.com>
Co-authored-by: Joel Challis <git@zvecr.com>
Co-authored-by: Joel Challis <git@zvecr.com>
Co-authored-by: Joel Challis <git@zvecr.com>
Co-authored-by: Joel Challis <git@zvecr.com>
Description
add support for v2 of the PCB using rp2040
Types of Changes
Issues Fixed or Closed by This PR
Checklist