Show advanced fusing status about lk2nd

[stephan-gh]

How much do we know (or do we need to know) about the layout of the fuse addresses/bits? Is this platform-specific? Will it need adjustment for every SoC supported in lk2nd?

Regarding the UI screen, I think it would be easier to start with a fastboot command that parses or possibly just dumps this (with parsing in a separate tool?). I think we don't have any consistent way at the moment to display additional screens. If wanted, this could be added later as a second step.

[fxsheep]

How much do we know (or do we need to know) about the layout of the fuse addresses/bits?Is this platform-specific? Will it need adjustment for every SoC supported in lk2nd?

Yes, this is platform specific. For msm8916, all listed above are documented publicly in the TRM(lm80-p0436-100_d_snapdragon_410e_apq8016e_tech_reference_manual_revd.pdf, page 3323), except binning, which is mostly documented in different pieces of CAF kernel sources.

For other platforms, AFAIK, Qualcomm tends to keep backward compatibility, which means the addresses can be cross-referenced from msm8916. This leaves verification a bigger problem though, since QFPROM should be considered static, and it's hard to 'test' the actual meaning.

However, this is actually more a legal problem than a technical one. Years have passed and these offsets are no longer a top secret, and people have been using addresses that come out of nowhere, e.g. here.

possibly just dumps this

TrustZone address protection on QFPROM is not contiguous and LK has to know where to dump from, so I think it's more reasonable to implement parsing on LK and print human-readable results.