Closed tannewt closed 8 months ago
We should go further with this as we have more boards with displays that aren't supported by displayio.Display()
. (Dotclock displays use FramebufferDisplay
for example. We should split displayio.Display
out as well as Epaperdisplay
.
displayio.Display
support LCD and OLED displays that have driver ICs with onboard framebuffer RAM. We should rename it to reflect that.
Also, should we split out the different display busses as well?
Also, should we split out the different display busses as well?
That makes sense because paralleldisplay is already split out unless it would be more overhead.
Can we use busdisplay
instead of externalframebufferio
?
Can we use
busdisplay
instead ofexternalframebufferio
?
Ya, totally open to different module names.
This will save space on boards that have an existing display and are unlikely to have an external epaper display (like pew pew m4).