Quote:
Originally Posted by WaseemAlkurdi
Great work! Absolutely great!
I have a question ... would it work with Kindles with 256 MB of RAM?
The KT2 (Kindle 7th generation) which I own has the same capable CPU as on the Paperwhite, but not the same amount of RAM (256 MB vs 512 MB). Would this be an issue?
|
Thank you! It should work, but webbrowsing will probably be an issue. Desktop only + htop amount to 140MB. Desktop + Chromium with 1 light tab open (mobileread.mobi) is 240MB already..
Quote:
Originally Posted by NiLuJe
@schuhumi: I'll be mildly curious to know, once people with a PW4/KOA2/KT4 try this, whether ordered dithering actually behaves as expected  .
It *should* (and it certainly does on similar Kobo HW), but when we enabled it in KOReader, we got reports about extremely broken quantization... :/.
(It's fairly easy to check with the fbink CLI tool and a random image, FWIW ). |
Haha that's just a random value I plugged in there for whatever reason and then forgot about it.. As far as I can see there's no way to see any dithering with fbink_refresh on a PW3 because HWD_* is unsupported and "fbink_cfg: Pointer to an FBInkConfig struct. Honors wfm_mode, is_nightmode, is_flashing" i.e. doesn't honor sw_dithering? To be brutally honest I haven't yet understood what the benefit is, probably just for A2 right?
Also after a A2 refresh the only way to get rid of ghosting is probably "is_flashing=true;"? A2 is really cool for scrolling (yay this whole things allows for all waveforms to be used
), but the flashing afterwards when drawing with WFM_GC16_FAST is kinda offputting. I would like to also put in some semi-smart optimization like A2 refreshes when a lot of damage events come in (or when the user drags the finger on the screen), and then do a high quality refresh afterwards..