You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Installing the QMK-CLI fails to install using brew on my system, and installing it via Pip requires additional packages, so I created a distrobox to install the CLI flasher via pip and the necessary packages. However, inside a user distrobox container there is no (good ux) way to run the CLI as root to access the USB device, hence the need for udev rules.
Warning!
These rules need to be evaluated very carefully. These rules apply to any microcontroller with the necessary ids, not just keyboards. There is likely a superset of these rules which would cover this case and allow flashing for Arduino and such. I was unable to find one with some quick searching but it may be worth investigating.
I somewhat recall running into a conflict with this years ago, and looking at the qmk firmware repo there are several issues which mention these rules causing issues:
I would like to propose adding the necessary udev rules to allow flashing QMK compatible keyboards as a non-root user.
The starting point for these rules is located here:
https://github.com/qmk/qmk_firmware/blob/master/util/udev/50-qmk.rules
Installing the QMK-CLI fails to install using brew on my system, and installing it via Pip requires additional packages, so I created a distrobox to install the CLI flasher via pip and the necessary packages. However, inside a user distrobox container there is no (good ux) way to run the CLI as root to access the USB device, hence the need for udev rules.
Warning!
These rules need to be evaluated very carefully. These rules apply to any microcontroller with the necessary ids, not just keyboards. There is likely a superset of these rules which would cover this case and allow flashing for Arduino and such. I was unable to find one with some quick searching but it may be worth investigating.
I somewhat recall running into a conflict with this years ago, and looking at the qmk firmware repo there are several issues which mention these rules causing issues:
The text was updated successfully, but these errors were encountered: