On Wed, Jun 14, 2017 at 05:53:47PM +0300, Pantelis Antoniou wrote:
fdtdump output can be very hard to read;
This patch makes sure that escaped characters are correctly detected
as strings and that output respects a given column width.
I really wish people would stop trying to use fdtdump as something
it's not. It's a trivial debug tool, nothing more. Options for
pretty don't belong here. If you want nicer dtb->dts output, use dtc
-I dtb -O dts.
Pantelis Antoniou (3):
util: Add method for escape output handling
fdtdump: Prettify output of properties
manual: Document prettification fdtdump options
Documentation/manual.txt | 2 +
fdtdump.c | 103 ++++++++++++++++++++++++++++++++++++++++++++---
util.c | 70 +++++++++++++++++++++++++++++++-
util.h | 35 ++++++++++++++++
4 files changed, 204 insertions(+), 6 deletions(-)
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson