View Single Post
Old 09-30-2023, 05:46 PM   #22
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
Quote:
Originally Posted by elinkser View Post
But there's something {among many other things) that still troubles me.
The Pocketbook lineup appears to be largely Allwinner, like the dreaded Sage/Elipsa:
No clue how that currently stands, but, when they moved to AW (on much older SoCs than the one used by the Sage/Elipsa, FWIW), they wrote a driver shim that (badly) translated the public mxcfb API to the (crappy) v1 AW display API.

We tried to live with it for a while in KOReader, but it required a gigantic and brittle pile of hacks, so we simply caved in and now go through the native middleware (InkView).

FBInk doesn't (as much as possible, we still use it for device identification, although that can be disabled, because bringing in InkView introduces brand new ways to break stuff in fun and interesting ways), and still includes the bare minimum of said pile of hacks.

TL;DR: It works. Not well, but it "works". In any case, definitely *not* an example to follow.

Last edited by NiLuJe; 09-30-2023 at 05:49 PM.
NiLuJe is offline