Search
370 results for “zmk”
-
The new Firefox 151.0 release adds support for the Web Serial API. This unlocks the ability to use ZMK Studio! There's some obvious rendering funkiness that will need addressing, but the core transport seems to work without issue!
Release notes: https://www.firefox.com/en-US/firefox/151.0/releasenotes/
-
Sometimes, my day gets really surreal out of nowhere: https://youtu.be/rgZlzCd0DUU?t=1819&si=9aPL7w7zyXmmEdFa
-
Sometimes, my day gets really surreal out of nowhere: https://youtu.be/rgZlzCd0DUU?t=1819&si=9aPL7w7zyXmmEdFa
-
Sometimes, my day gets really surreal out of nowhere: https://youtu.be/rgZlzCd0DUU?t=1819&si=9aPL7w7zyXmmEdFa
-
Sometimes, my day gets really surreal out of nowhere: https://youtu.be/rgZlzCd0DUU?t=1819&si=9aPL7w7zyXmmEdFa
-
one more ZMK module is out. this one is a replacement for the stock temp-layer behaviour. it does all the smart things with mouse buttons workflows and such. https://github.com/kaievns/zmk-mouse-layer
-
one more ZMK module is out. this one is a replacement for the stock temp-layer behaviour. it does all the smart things with mouse buttons workflows and such. https://github.com/kaievns/zmk-mouse-layer
-
one more ZMK module is out. this one is a replacement for the stock temp-layer behaviour. it does all the smart things with mouse buttons workflows and such. https://github.com/kaievns/zmk-mouse-layer
-
also, opensourced my custom ZMK input processors optimised for trackball data processing. mouse acceleration, smoothing, fully featured mouse layers support, etc.
-
also, opensourced my custom ZMK input processors optimised for trackball data processing. mouse acceleration, smoothing, fully featured mouse layers support, etc.
-
also, opensourced my custom ZMK input processors optimised for trackball data processing. mouse acceleration, smoothing, fully featured mouse layers support, etc.
-
published my latest pmw3610 optical sensor driver for ZMK as a stand alone module https://github.com/kaievns/pmw3610-zmk-driver
-
published my latest pmw3610 optical sensor driver for ZMK as a stand alone module https://github.com/kaievns/pmw3610-zmk-driver
-
i think i'm done with my new ZMK firmware. chucked it on GH.
btw, it has a _very_ nice new pmw3610 driver, and a bunch of custom input processors to make trackball movements buttery smooth https://github.com/kaievns/5deg-zmk-firmware #zmk #keyboard #opensource
-
i think i'm done with my new ZMK firmware. chucked it on GH.
btw, it has a _very_ nice new pmw3610 driver, and a bunch of custom input processors to make trackball movements buttery smooth https://github.com/kaievns/5deg-zmk-firmware #zmk #keyboard #opensource
-
i think i'm done with my new ZMK firmware. chucked it on GH.
btw, it has a _very_ nice new pmw3610 driver, and a bunch of custom input processors to make trackball movements buttery smooth https://github.com/kaievns/5deg-zmk-firmware #zmk #keyboard #opensource
-
. @zmk builds on GitHub Actions have always been uploading artifacts as "firmware.zip". It has always been utter annoying to me.
So I wrote a small GitHub Actions workflow to overcome this: It adds built firmware files to the release as separate files, just like QMK does:
https://github.com/Ardakilic/zmk-config/commit/0a04b0106389c2517413cfe9c695939bd17d5cf8
Example release:
https://github.com/Ardakilic/zmk-config/releases/tag/latest
Might be useful for you. It definitely will be for me :)
I wish this was in core ZMK thogh.
-
. @zmk builds on GitHub Actions have always been uploading artifacts as "firmware.zip". It has always been utter annoying to me.
So I wrote a small GitHub Actions workflow to overcome this: It adds built firmware files to the release as separate files, just like QMK does:
https://github.com/Ardakilic/zmk-config/commit/0a04b0106389c2517413cfe9c695939bd17d5cf8
Example release:
https://github.com/Ardakilic/zmk-config/releases/tag/latest
Might be useful for you. It definitely will be for me :)
I wish this was in core ZMK thogh.
-
. @zmk builds on GitHub Actions have always been uploading artifacts as "firmware.zip". It has always been utter annoying to me.
So I wrote a small GitHub Actions workflow to overcome this: It adds built firmware files to the release as separate files, just like QMK does:
https://github.com/Ardakilic/zmk-config/commit/0a04b0106389c2517413cfe9c695939bd17d5cf8
Example release:
https://github.com/Ardakilic/zmk-config/releases/tag/latest
Might be useful for you. It definitely will be for me :)
I wish this was in core ZMK thogh.
-
. @zmk builds on GitHub Actions have always been uploading artifacts as "firmware.zip". It has always been utter annoying to me.
So I wrote a small GitHub Actions workflow to overcome this: It adds built firmware files to the release as separate files, just like QMK does:
https://github.com/Ardakilic/zmk-config/commit/0a04b0106389c2517413cfe9c695939bd17d5cf8
Example release:
https://github.com/Ardakilic/zmk-config/releases/tag/latest
Might be useful for you. It definitely will be for me :)
I wish this was in core ZMK thogh.
-
. @zmk builds on GitHub Actions have always been uploading artifacts as "firmware.zip". It has always been utter annoying to me.
So I wrote a small GitHub Actions workflow to overcome this: It adds built firmware files to the release as separate files, just like QMK does:
https://github.com/Ardakilic/zmk-config/commit/0a04b0106389c2517413cfe9c695939bd17d5cf8
Example release:
https://github.com/Ardakilic/zmk-config/releases/tag/latest
Might be useful for you. It definitely will be for me :)
I wish this was in core ZMK thogh.
-
A @zephyr driver that's been a long time coming... https://github.com/zephyrproject-rtos/zephyr/pull/106336
RGB support on stm32 has been a frequent request from that small subset of folks running #ZMK on wired boards. Rarely had the SPI based driver worked with the pins used by most designs, so when I saw https://github.com/zephyrproject-rtos/zephyr/pull/88671 get merged, I immediately jumped into an led_strip driver using it!
It's fairly straightforward, using DMA to feed in a sequence of compare values that correspond to the necessary bit value to send.
-
A @zephyr driver that's been a long time coming... https://github.com/zephyrproject-rtos/zephyr/pull/106336
RGB support on stm32 has been a frequent request from that small subset of folks running #ZMK on wired boards. Rarely had the SPI based driver worked with the pins used by most designs, so when I saw https://github.com/zephyrproject-rtos/zephyr/pull/88671 get merged, I immediately jumped into an led_strip driver using it!
It's fairly straightforward, using DMA to feed in a sequence of compare values that correspond to the necessary bit value to send.
-
A @zephyr driver that's been a long time coming... https://github.com/zephyrproject-rtos/zephyr/pull/106336
RGB support on stm32 has been a frequent request from that small subset of folks running #ZMK on wired boards. Rarely had the SPI based driver worked with the pins used by most designs, so when I saw https://github.com/zephyrproject-rtos/zephyr/pull/88671 get merged, I immediately jumped into an led_strip driver using it!
It's fairly straightforward, using DMA to feed in a sequence of compare values that correspond to the necessary bit value to send.