Recent work in pcd68-on-esp32 demonstrates the real epaper interface... during that development, it seems that perhaps a more efficient solution for the PCD-68 computer is to expose the refresh/busy control directly via "registers" in the Screen peripheral -- so that the 68k code would be required (or merely allowed?) to be explicitly set in order to trigger a screen refresh cycle. Maybe allow that control byte/register to allow for a "quick" or "partial" refresh? Or abstract this part? Should there be a set interval for screen refreshes? A very slow (but guaranteed) refresh rate?
Recent work in pcd68-on-esp32 demonstrates the real epaper interface... during that development, it seems that perhaps a more efficient solution for the PCD-68 computer is to expose the refresh/busy control directly via "registers" in the Screen peripheral -- so that the 68k code would be required (or merely allowed?) to be explicitly set in order to trigger a screen refresh cycle. Maybe allow that control byte/register to allow for a "quick" or "partial" refresh? Or abstract this part? Should there be a set interval for screen refreshes? A very slow (but guaranteed) refresh rate?