View Single Post
Old 10-26-2018, 07:06 PM   #235
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Okay, a final comment on the smem_len thing:

Someone (@pazos) recently ported FBink to BQ/Cervantes devices (which are based on the same NTX hardware as Kobos), and reported weird softlocks after a screen clear over the stock reading app.

I was doing that with a simple smem_len memset.

Turns out, when it can (i.e., @ 16bpp), the Qt Embedded driver they (and possibly others) use uses memory from the offscreen buffer to do... stuff.
I'm too lazy to dig into this much (c.f., https://github.com/bq/cervantes-qt/b...kfb/einkfb.cpp, size/psize vs. mapsize), so I'll be switching that memset to line_len * yres (and not yres_virtual like I'd like, because apparently Qt starts monopolizing memory potentially earlier than that).

AFAICT, the mmap is perfectly fine, though .

Last edited by NiLuJe; 10-26-2018 at 07:12 PM.
NiLuJe is offline   Reply With Quote