Christian

The compiler [suggests](https://github.com/tvheadend/tvheadend/actions/runs/14956836403/job/42013633668#step:3:1664) using `vld1q_s64` instead of `vld1q_s16_x4`.

The build logs differ from each other, so `vld1q_s64` might not available everywhere and is probably no common fix. [gcc#71233](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71233) lists `vld1q_s16_x4` as unavailable in gcc. Newer versions contain if...

Nice. I didn't notice that the failing builds all occur on older distros. Then it might indeed be appropriate to exclude x265 from these.

You're welcome. I hope this unblocks some of the waiting PRs. Thanks for your quick reaction!

Thanks for joining! That sounds to me as if this feature could be implemented by introducing a new topic, e.g. `PassiveMode`, and sending `0xff` via SPI when enabled.

Thanks for joining! What do you mean by "disconnecting", physical removal of the wire or sending of a command?

No, I didn't remove the MISO wire.

I implemented passive mode in branch [passive-mode](https://github.com/absalom-muc/MHI-AC-Ctrl/compare/master...git-developer:MHI-AC-Ctrl:passive-mode). When enabled, MQTT commands have no effect on the AC device: ``` $ mosquitto_sub -v -L mqtt://broker/MHI-AC-Ctrl/# & $ mosquitto_pub -L mqtt://broker/MHI-AC-Ctrl/set/PassiveMode -m...

@hberntsen Is it possible to toggle active/passive mode at runtime, without a power cycle? Can you confirm that the AC device must be in passive mode on power on?

You should be able to find a workaround for your arch, too. The required interpreter can be detected by ```sh readelf -a "$(command -v python3)" | grep -i requesting ```...