Probably the best way to support SPI type displays (or other displays with their own frame buffer) is to write your own replacement for src/fbufvdu.c. You need to supply versions of the following routines:But for other display types it looks like it would get messy pretty quickly. I intended to just fudge mode changes anyway so a particular display would have a correct mode and other ...less than correct modes.
Given that writing to the display is done via what I guess we'd call ROM routines, even adding a dirty bit or something for when the display updates would be enough to really cut down on bandwidth usage.
Code:
void getcsr(int *px, int *py);int vpoint (int xp, int yp);int vtint (int xp, int yp);int vgetc (int x, int y);int widths (unsigned char *s, int l);void xeqvdu (int code, int data1, int data2);
Statistics: Posted by Memotech Bill — Mon Nov 11, 2024 8:39 am