View Single Post
Old 01-19-2015, 02:42 PM   #22
sadowski
Connoisseur
sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.sadowski ought to be getting tired of karma fortunes by now.
 
Posts: 84
Karma: 1142796
Join Date: Jul 2009
Device: Sony PRS 350, Kobo mini, PB mini
Quote:
Originally Posted by chrox View Post
Yes, it looks like the pitch size (bytes for a single line) is detected wrong, more precisely pitch size is less than actual one used in the framebuffer device otherwise the application would very likely have already crashed.

So you can just hack this line: https://github.com/koreader/koreader..._linux.lua#L64 in the "koreader/ffi/framebuffer_linux.lua" file at line 64:

until you make it right.
I agree, it must be the pitch size. I tried a few combinations of TYPE_BB4, ...8, ...16, etc. with different increments of the line length without seeing a way forward. It changes but not in the right way. Line length increments greater than +4 crash the program. Can it be that this display type ist not yet defined? Or somewhere else in the code?
sadowski is offline   Reply With Quote