View Single Post
Old 12-18-2011, 01:18 AM   #27
geekmaster
Carpe diem, c'est la vie.
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: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
FYI: The K4 and Touch use the framebuffer differently, allowing fewer assumptions such as 4 bpp. K4 and Touch are both 8 bpp. Also the Touch has an extra 8 bytes of padding after each line, and the Touch framebuffer contains more than twice as many "virtual" lines as screen lines.

The biggest problem with the touch is that it does not respond to ioctl calls to trigger display updates, and the /proc/ interface has been removed (or renamed). I do not yet know how to programmatically trigger a display update on the Touch.

These changes will affect existing kindle hacks.

More info here:
https://www.mobileread.com/forums/sho...d.php?t=161419

UPDATE:
I have been doing eink framebuffer updates with eips '' (two single quotes) in scripts, or I enclose that in a system() call in C programs, until I figure out a better way (such as an ioctl() call that I can get working reliably). You can see examples in my touchpaint and ddplot scripts published in other threads.

Last edited by geekmaster; 03-10-2012 at 02:01 PM.
geekmaster is offline   Reply With Quote