- maybe provide hints to the low level PAGE_NEXT function as to which area(s) are "dirty" and need updating.
After the first iteration, it could be known which pages are written. So, empty pages could be skipped. But instead of copying the page to the display, the page needs still to be cleared.
- Could it treat the page buffer as a write through cache instead?
not exactly sure what you mean about this.
- Could it create a full frame buffer to provide additional functionality?
Sure, this could be done (as long as there is enough SRAM)
Oliver