With the same CPU, so, yeah, that's nice, means a single binary for the whole K4/K5/KPW range .

Nice translation.

What follows is my translation as requested by ixtab:

Quote:

Originally Posted by knc1

This one is a bit easier to deal with than the older Kindles:

The (cross-) compiled, native executables in the Kindle version 5.2.0 firmware shipped first on the Kindle paperwhite device in October, 2012 shows build dates of September, 2012.

For the best chance of re-using the existing libraries and code already installed on the machine, the recommended practice is to use the same or a very similar tool-chain, library set, and compile time option set.

Examination of the binaries with recent build dates discovers the following about the tool-chain in use by the vendor:

The recommendation for doing "compatible work" is a choice of two courses:

Use the most recent Linaro tool-chain prior to the shift to armelhf as the standard:https://launchpad.net/linaro-toolcha...estone/2012.04
Or
Re-build an armel tool-chain from the least buggy, recent, tool-chain:https://launchpad.net/linaro-toolcha...estone/2012.09
By selecting the crosstool-ng bundle on that page and making the configuration changes required to select the tool-chain and libc default options that best match that of the vendor's tool-chain setup.
This second choice, even using the automated tool-chain builder, one that only those with experience in building system tool-chains and libraries should attempt.

As can be seen from the above link (which lists version details of the dependencies), probably the best recommendation that can be made here is to use the second choice above (crosstool-ng) and set its configuration to download and build the older, 2.6.12 system library set.
Be certain to also set the kernel headers selection to 2.6.16 (the prior "build ABI standard") in the crosstool-ng configuration for the system libraries.

Note: The same comments above apply to using Buildroot (which can use crosstool-ng for its tool-chain building).

I am going to work on the DX(g) de-brick research first, before adding things to my own site.

twobob is an "editor" - he could add the structure entries for B024, hardware and firmware.
Any member can edit the page contents, it is only changing the structure itself (not its content) that requires "editor" permission.