It means that some practical
details of the implementation of the display technology are 'leaking' up
into the graphics abstraction, but I don't really see a way to avoid it.
Only the application knows when it's permissible to take an extended
time to perform an update.
How are other operating systems / graphics libraries handling this?
I can imagine how minimal RTOS and bare metal solutions would do this --
via calls into hodge podge HAL. But that would not apply to a POSIX OS
which constrains application interfaces to only portable interfaces.
If Linux/Android supports this device, how they did this would be
meaningful. If you provide the display info, I can check of there is
support by other higher-level OSs. I generally accept how-linux-does-it
as good as a specification in lack of any real specification.
[Although I really don't like looking at Linux drivers these days. The
Linux driver sub-subsystem has gotten very complex and I stopped keeping
up with Linux internals years ago].
Greg
