View Single Post
Old 09-15-2015, 08:23 AM   #37
knc1
Going Viral
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: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
I happened to notice this snippet:
Code:
/*
 * DisplayLink HW has separate 16bpp and 8bpp framebuffers.
 * In 24bpp modes, the low 323 RGB bits go in the 8bpp framebuffer
 */
Since the e-ink devices are grayscale, you would probably get a much nicer display if you dithered 888 to 323 encoding rather than a simple truncate.

For inspiration:
Geekmaster posted some very fast dither code here (un-maintained).
And KOReader uses dither code.

Q?:
Does the DXG even have 8bpp frame buffer?
Or is it one of the Kindle 4bpp frame buffers, with tricky packing to 1 byte per pixel?
knc1 is offline   Reply With Quote