View Single Post
Old 02-23-2012, 11:28 AM   #7
knc1
\_(ツ)_/ <- Clueless
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 11,831
Karma: 12397053
Join Date: Feb 2012
Location: Central Texas
Device: No PW2, KV, KOA
Quote:
Originally Posted by geekmaster View Post
K4 (Kindle 4 non-touch) and K5 (Kindle touch) use the framebuffer in a different way than the K3 and earlier devices.
Been a few variations in the hardware eink drivers also:
Code:
root:cat$ grep 'drivers/video/eink' Amazon_2012.02.18_sha1.cat | sort --key=1.1,1.40 -u | wc -l
198
May take some time to sort out what are simply kernel-version changes and what are functional changes.
But going by the pathnames and filenames - there have been several __different__ driver organizations.

True - the directFB layer is __supposed to__ hide those changes, but....
knc1 is online now   Reply With Quote