ACCESS.bus: The Forgotten USB Competitor
tedium.co
tedium.co
- Small EEPROMs, often used for configuration data or small firmware blobs
- MEMS sensors (accelerometers, gyroscopes, etc)
- Small LCD/OLED displays (e.g. 128x64)
- Configuration ports on devices which use other busses for bulk data (e.g. display drivers, audio codecs, etc).
https://www.ddcutil.com/#ddcui
Also, if you have ddcci-driver-linux installed, then the KDE desktop lets you adjust monitor brightness from the UI. Eventually Linux upstream might get the same functionality as the out-of-tree module.
systemctl --user edit plasma-powerdevil.service
[Service]
Environment="POWERDEVIL_NO_DDCUTIL=1"
EDIT: I tried switching to Wayland on Arc and am getting stuttery mouse cursor movement at around 36 FPS. I wonder what's wrong...The best thing was certain macbooks not working at a certain input. It the turns out HDCP was at fault, which is basically DRM for HDMI.
Compare this to USB, which has fixed timing (once you get the bus, you have to respond in time or release bus without sending anything). Moreover, all USB traffic is sent via hubs - so if device is misbehaving, hubs can cut it off without affecting the rest. The spec even has provisions for cutting off the power to misbehaving device, but most cheap hubs do not implement this.
I couldn’t find any info back in the day beyond that it was I2C-based, but appreciate being able to connect the dots now.