Drop the 0x from what Peek, Poke and Hexdump print

Two columns back, and a better reason than the two columns.

Every number these words read is hex - there is no other kind, and they refuse a decimal
one - so a prefix on the output restates what the whole file already says. Dropping it buys
something worth more than the width: an address in a dump can be typed straight back into a
Peek without editing it, because bare hex is exactly what the parser now wants. Output that
is valid input beats output that is decorated.

No platform question to answer either: `enabled` is freestanding-and-not-wasm, so these
three words exist only on bare metal. There is no host format to stay consistent with.

On the die, 44 columns of a 48-column body:

    40000020  32 54 cd ab  00 00 00 00  |2T......|
    40000030  30 2e 31 00  00 00 00 00  |0.1.....|

    5011002c: wrote deadbeef, reads deadbeef
    5011002c: deadbeef
    501101a4: fc48777d
    501101a4: 4b4ae238

The last two are the same command twice - LP_SYSTEM_REG_RNG_DATA, which is what makes it
the honest demonstration that a register is not memory.

unit-test, and `p4-bench --check` 4/4 on the board.

0 files changed, 0 insertions, 0 deletions