View Single Post
Old 11-11-2020, 01:50 PM   #2
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
The device is likely too underpowered to make anything modern remotely usable, unless you keep it CLI only, in which case, you don't really have to bother as it's already running Linux and getting a root shell is trivial?

----

Otherwise, look at the Alpine images for K5 & up. Which are already dog slow, despite running on much more powerful hardware.

----

Sidebar: You're absolute *NOT* going to be able to use anything other than Amazon's own kernel sources. Even on more modern devices, which are at least based on NXP's own kernel trees, rebasing against newer versions of said tree is a *massive* endeavor, and rebasing against anything more different than that is basically pure masochism.

You don't see a lot of custom kernels for consumer eInk devices, there's a reason for that .

Last edited by NiLuJe; 11-11-2020 at 01:54 PM.
NiLuJe is offline   Reply With Quote