home.social

Search

370 results for “zmk”

  1. 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: firefox.com/en-US/firefox/151.

  2. 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. github.com/kaievns/zmk-mouse-l

    #zmk #keyboard #opensource

  3. 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. github.com/kaievns/zmk-mouse-l

    #zmk #keyboard #opensource

  4. 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. github.com/kaievns/zmk-mouse-l

    #zmk #keyboard #opensource

  5. also, opensourced my custom ZMK input processors optimised for trackball data processing. mouse acceleration, smoothing, fully featured mouse layers support, etc.

    github.com/kaievns/zmk-trackba

    #zmk #keyboard #opensource

  6. also, opensourced my custom ZMK input processors optimised for trackball data processing. mouse acceleration, smoothing, fully featured mouse layers support, etc.

    github.com/kaievns/zmk-trackba

    #zmk #keyboard #opensource

  7. also, opensourced my custom ZMK input processors optimised for trackball data processing. mouse acceleration, smoothing, fully featured mouse layers support, etc.

    github.com/kaievns/zmk-trackba

    #zmk #keyboard #opensource

  8. @hbons I've long dreamed of #ZMK getting a "proper" logo (not just for our studio app, but for the project as a whole, usage in social media, etc)

    Is that the kind of thing you help projects with?

  9. @hbons I've long dreamed of getting a "proper" logo (not just for our studio app, but for the project as a whole, usage in social media, etc)

    Is that the kind of thing you help projects with?

  10. @hbons I've long dreamed of #ZMK getting a "proper" logo (not just for our studio app, but for the project as a whole, usage in social media, etc)

    Is that the kind of thing you help projects with?

  11. @hbons I've long dreamed of #ZMK getting a "proper" logo (not just for our studio app, but for the project as a whole, usage in social media, etc)

    Is that the kind of thing you help projects with?

  12. @hbons I've long dreamed of #ZMK getting a "proper" logo (not just for our studio app, but for the project as a whole, usage in social media, etc)

    Is that the kind of thing you help projects with?

  13. 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 github.com/kaievns/5deg-zmk-fi #zmk #keyboard #opensource

  14. 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 github.com/kaievns/5deg-zmk-fi #zmk #keyboard #opensource

  15. 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 github.com/kaievns/5deg-zmk-fi #zmk #keyboard #opensource

  16. @rayk yeah, my biggest concern there is mostly going to be sane mapping of devices into the container(s) for #zephyr / #zmk for flashing, twister, etc.

  17. . @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:

    github.com/Ardakilic/zmk-confi

    Example release:

    github.com/Ardakilic/zmk-confi

    Might be useful for you. It definitely will be for me :)

    I wish this was in core ZMK thogh.

    #zmk #qmk #mechanicalkeyboard #githubactions

  18. . @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:

    github.com/Ardakilic/zmk-confi

    Example release:

    github.com/Ardakilic/zmk-confi

    Might be useful for you. It definitely will be for me :)

    I wish this was in core ZMK thogh.

    #zmk #qmk #mechanicalkeyboard #githubactions

  19. . @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:

    github.com/Ardakilic/zmk-confi

    Example release:

    github.com/Ardakilic/zmk-confi

    Might be useful for you. It definitely will be for me :)

    I wish this was in core ZMK thogh.

    #zmk #qmk #mechanicalkeyboard #githubactions

  20. . @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:

    github.com/Ardakilic/zmk-confi

    Example release:

    github.com/Ardakilic/zmk-confi

    Might be useful for you. It definitely will be for me :)

    I wish this was in core ZMK thogh.

    #zmk #qmk #mechanicalkeyboard #githubactions

  21. . @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:

    github.com/Ardakilic/zmk-confi

    Example release:

    github.com/Ardakilic/zmk-confi

    Might be useful for you. It definitely will be for me :)

    I wish this was in core ZMK thogh.

    #zmk #qmk #mechanicalkeyboard #githubactions

  22. A @zephyr driver that's been a long time coming... github.com/zephyrproject-rtos/

    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 github.com/zephyrproject-rtos/ 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.

  23. A @zephyr driver that's been a long time coming... github.com/zephyrproject-rtos/

    RGB support on stm32 has been a frequent request from that small subset of folks running on wired boards. Rarely had the SPI based driver worked with the pins used by most designs, so when I saw github.com/zephyrproject-rtos/ 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.

  24. A @zephyr driver that's been a long time coming... github.com/zephyrproject-rtos/

    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 github.com/zephyrproject-rtos/ 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.