View Single Post
Old 07-07-2018, 07:05 PM   #1
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
Lightbulb Call for testers with a Mark 7 device

To make a long story short: those devices expose a slightly tweaked interface to talk with the eInk controller, and I'd like to make sure we're doing it right in KOReader.

Right now, since no-one has come at us with pitchforks, current FW appear to still handle the older interface, but this may not hold true forever (although, given Kobo's track record, I doubt it will actually change, but, no matter).

The code is already written, it's just disabled until I have more details to make sure it's correct. That's where you come in!

You basically just need shell access to your device (be it telnet or SSH) *under Nickel*.

You don't necessarily need a deep understanding of the *nix CLI, but, of course, that's always a plus .

If that's you, the gory details are explained in the relevant KOReader issue.

Thanks!
NiLuJe is offline   Reply With Quote