Philip Howard

Feel free to open a PR- though I’m going to have to do some careful inspection of our i2c-device based libraries to make sure I’m not wrong 😬

#63 should finally put this to rest... I think! I'm not actually totally sure.

With the arrival of Raspberry Pi Pico we hope to *write* one, but this wont be for a while.

You should be using `i2c-detect -y 0` if you want the i2c bus on the board. I don't think the i2c bus it uses is *entirely* predictable, but you can...

There should not be two i2c busses- the external i2c pins on the header are connected to the same physical pins as the touch controller. i2c is a multi-drop bus,...

This should not be too difficult to implement, all of the logic to read/write from the underlying i2c device is implemented by `_i2c_read` and `_i2c_write` functions: https://github.com/pimoroni/i2cdevice-python/blob/60bfa6a989b3f135be84091a95e8af949a8f7034/library/i2cdevice/__init__.py#L281-L291 These would have...

All of our display products need kms panel drivers, so full support on Bullseye is probably not going to happen this side of next year. It's a *lot* of work...

> If someone paid for the implementation of Bullseye support for this hardware, would that make a difference? Regrettably I’ve still not found a way to turn money into time....

This works fine if I power Keybow directly, so it must be some interaction between Keybow -> Hub -> Host. Possibly blipping the power supply enough to crash the Pi,...

Tested with an ORICO HF9US and it works fine if I disconnect/reconnect the hub from the host PC. I'm afraid this is more likely to be an unavoidable electrical issue-...