#[Solved] Update to 4.1 but ran into pmw3610 driver devicetree error?

1 messages · Page 1 of 1 (latest)

vast rune
#

The regular one configured okay, but the peripheral that has a trackball module has a conflict between sensor drivers?
https://github.com/kaihchang/zmk-config-kai-cosmos-dongle/actions/runs/20099245032/job/57665477005
devicetree error: both /tmp/zmk-config/zmk-pmw3610-driver/dts/bindings/pixart,pmw3610.yml and /tmp/zmk-config/zephyr/dts/bindings/input/pixart,pmw3610.yaml have 'compatible: pixart,pmw3610' and 'on-bus: spi'

In west.yml, I'm using
projects: - name: zmk remote: zmkfirmware revision: main import: app/west.yml - name: zmk-pmw3610-driver remote: efogdev revision: main - name: zmk-input-processor-report-rate-limit remote: badjeff revision: main - name: zmk-input-processor-xyz remote: badjeff revision: main - name: zmk-pointing-acceleration remote: oleksandrmaslov revision: main

Might not even be a ZMK update issue. I just can't find what are conflicting for now. This didn't show up 3 months ago.

GitHub

Dongle mode for Kai Cosmos trackball keyboard. Contribute to kaihchang/zmk-config-kai-cosmos-dongle development by creating an account on GitHub.

rough tangle
#

You need to specify zephyr-4.1 branch instead of main for the driver; then replace compatible = "pixart,pmw3610" with compatible = "pixart,pmw3610-efogtech"

vast rune
#

Oh yeah, Efog for the rescue!

#

Thx for saving me lots of time