View Single Post
Old 02-29-2024, 02:39 AM   #4
wold
Zealot
wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.wold knows better than to ask about the Gravitic Imploder Lance.
 
Posts: 121
Karma: 87007
Join Date: Apr 2021
Device: Lux 5, Libra 2, PRS-T2N
Quote:
Originally Posted by jrw174 View Post
Probably not exactly what you are looking for, but this documentation seems to have some of the pin outs

https://linux-sunxi.org/PocketBook_Touch_Lux_3
Interesting page.

So there's a lot more to updating the display than just pushing bytes to some buffer (re the Inkpad4/5 discussion):

Quote:
Instead of pushing all the complexity of parsing waveform data and figuring out what to do to move the ink from a current position to a new one to kernel space, the driver provides the base interface for writing a precisely timed frame to the display. Waveform parsing, temperature adjustment of timings, and choosing an algorithm to update different regions of the display is left to the userspace, where it can be much more easily experimented with and used to provide the best experience based on what content is displayed in what regions of the screen.
wold is offline   Reply With Quote