Closed jerbzz closed 1 year ago
I'll raise this with production, I think the EEPROM data was prepared before we had the pleasant surprise of discovering the display was higher resolution... yep suddenly finding out your display is a different resolution to the old part is a thing that happens with E-Ink :laughing:
Hi,
When running
identify.py
from the examples, I get this output on my two pHATs:The resolution for the Yellow (SSD1608) pHat is incorrect - it should be 250x122.
I can see that the resolution appears to be read directly from the EEPROM in
eeprom.py
. The class instance returned from inky.auto does return the correct resolution/width/height for both boards, but this appears to be hardcoded inphat.py
and elsewhere.Not sure how much this matters, but it bothered me 😁