-
Notifications
You must be signed in to change notification settings - Fork 41
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
Teensy 3.2 (kint32) QMK support #2
Comments
I’ll close this as there hasn’t been any user interest in the |
I have 3 teensy 3.2s collecting dust. Will these work or no? Can it be fixed in qmk? Thanks |
I haven’t tested yet, as nobody expressed any interest before you.
It would need to be added to qmk first. Could be a simple copy of kint36, but there’s no way of telling whether it will really work unless someone tries it :) |
Ok, cool. I'll report back.
Doing a 3.6 one right now. A 3.2 is next.
Le mer. 30 juin 2021 à 12:41, Michael Stapelberg ***@***.***>
a écrit :
… Will these work or no?
I haven’t tested yet, as nobody expressed any interest before you.
Can it be fixed in qmk?
It would need to be added to qmk first. Could be a simple copy of kint36,
but there’s no way of telling whether it will really work unless someone
tries it :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3QXMVOFPIHU33LU4XPCWDTVNCJ5ANCNFSM4OVJYTJA>
.
|
You can try https://github.com/kinx-project/qmk_firmware/commits/kint32. |
This has been working for me for some time now. It worked out of the box.
I have a version of my keymap for it to push at some point.
If I just replace the bouncy keys...
Le mer. 30 juin 2021 à 15:28, Michael Stapelberg ***@***.***>
a écrit :
… You can try https://github.com/kinx-project/qmk_firmware/commits/kint32. make
kinesis/kint32:stapelberg works for me, but I haven’t tested the
resulting firmware on an actual Teensy 3.2.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3QXMTUWR4OW7NXFFENX23TVNV6BANCNFSM4OVJYTJA>
.
|
Would you mind doing a PR to add the kint32 to Qmk ? I've got a few of these now. |
I don’t have time to test the kint32 properly now or going forward. If you want to have the support merged into QMK, can I suggest you take the branch posted above as a starting point, and contribute it to QMK yourself please? Thanks |
OK, that works. I didn't want to do that without your permission. I Don't know when I'll get to it either. But I will do it. Thank you, Have a nice day. EricEnvoyé depuis ma tablette Huawei-------- Message original --------De : Michael Stapelberg ***@***.***>Date : sam. 29 janv. 2022 à 09:58À : kinx-project/kint ***@***.***>Cc : Eric Gebhart ***@***.***>, Comment ***@***.***>Objet : Re: [kinx-project/kint] Teensy 3.2 (kint32) QMK support (#2)
I don’t have time to test the kint32 properly now or going forward.
If you want to have the support merged into QMK, can I suggest you take the branch posted above as a starting point, and contribute it to QMK yourself please?
Thanks
—Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you commented.Message ID: ***@***.***>
|
No description provided.
The text was updated successfully, but these errors were encountered: