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.