Keychron keyboards firmware upgrade support

[marcosps]

Describe the question
Do you have plans to add support for keychron keyboards? I'm asking because I opened a bug on HID kernel modules about a warning that I'm seeing, and it's possible that it's related to the keyboard firmware.

Either way, I sent a message to Keychron contact web page about fwupd support, but no answer yet.

Thanks in advance!

[hughsie]

There's no plan right now, but there are a few people interested in implementing this. Unless we can get buy-in from Keychron to upload firmware to the LVFS I don't think there's a lot of point adding a plugin IMHO.

[hughsie]

Can you grab the full dfu-util command line from anywhere? It might just work :)

[marcosps]

Would that work even without QMK support? My keyboard is a simple K8 :)

[devurandom]

Would that work even without QMK support?

Probably not. :(

Can you grab the full dfu-util command line from anywhere? It might just work :)

I found the code responsible for the qmk flash command: https://github.com/qmk/qmk_firmware/blob/4e369d405af6bba1adce6337b2e1b1ea1788566c/lib/python/qmk/flashers.py
(Called from https://github.com/qmk/qmk_firmware/blob/4e369d405af6bba1adce6337b2e1b1ea1788566c/lib/python/qmk/cli/flash.py.)

You can find the firmware file of my keyboard behind the "Download K9 Pro ANSI RGB Version Firmware" button on https://www.keychron.com/blogs/archived/k9-pro-factory-reset-and-firmware-flash.
(Other keyboards' firmware is linked on https://www.keychron.com/pages/firmware, but not all of them use QMK.)
The source code for my keyboard is supposed to be https://github.com/Keychron/qmk_firmware/tree/bluetooth_playground/keyboards/keychron/k8_pro, but I did not try to build let alone flash it.

[hughsie]

Super useful. We support all those protocols already (uf2, dfu, dfuse, st-dfu, etc) with one exception: SAM-BA (which is what mdloader provides). I think the hard bit is to convince Keychron to test with fwupd, and upload firmware to the LVFS.

[devurandom]

I sent them an email with you, @hughsie, in CC. Please feel free to correct or amend anything I wrote in that email.