View Single Post
Old 12-18-2018, 06:11 PM   #8
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
On a mildly related notes:

The purely HW-specific bits (CPU, RAM, etc.) are in the NTX HWConfig tag found in a clump of bytes at the start of the block device.

You can decode the data on your own device via ntx_hwconfig, or you can implement the bits you need yourself to avoid calling that thing (it appears to be statically linked against the glibc, brr!).

Various generations of Kobo kernels source packages have more or less detailed info in the related header. Earlier kernels were messy, but a bit more verbose.

Last edited by NiLuJe; 12-18-2018 at 06:15 PM.
NiLuJe is offline   Reply With Quote