View Single Post
Old 10-06-2012, 06:22 PM   #16
geekmaster
Всё гениальное просто.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 5,070
Karma: 6789001
Join Date: Nov 2011
Location: Щедрость не имеет пределов.
Device: *.*
The error message from eips when displaying text off the end of a line shows that it is trying to use 768 pixels per line (xres_virtual) instead of 758 (xres). And yres_virtual shows that the framebuffer will hold 6 pages of data. My K5 had room for 2 pages of data, but twobob reported that his new K5 has a framebuffer that can hold 4 pages of data.

You can change the starting position of the displayed screen to any of those 6K framebuffer rows with by echoing the offset coords into a /sys/ file. And when scrolled, the system still uses offset zero. That way our native code could move the viewing window to the second page and use it without interference, while the system framework continues to use the hidden page zero...
geekmaster is offline   Reply With Quote