diff options
author | David Gibson <david@gibson.dropbear.id.au> | 2017-04-18 13:05:08 +1000 |
---|---|---|
committer | David Gibson <david@gibson.dropbear.id.au> | 2017-04-18 13:05:08 +1000 |
commit | 548aea2c436ab47ff09ba9ec7e902e971bbc399c (patch) | |
tree | 91684f7f59f86eb36a53824537a0f7ec582b63a1 | |
parent | c2258841a785742a3fd5c423f4965caac73d01af (diff) | |
download | dtc-548aea2c436ab47ff09ba9ec7e902e971bbc399c.zip dtc-548aea2c436ab47ff09ba9ec7e902e971bbc399c.tar.gz dtc-548aea2c436ab47ff09ba9ec7e902e971bbc399c.tar.bz2 |
fdtdump: Discourage use of fdtdump
fdtdump is, and always has been, a quick-and-dirty debugging tool. However
I keep getting reports of people using it for real work. For production
decompiling of a dtb, dtc in -I dtb -O dts mode is the right tool. In the
hopes of getting that message out there, add a warning message to fdtdump
to discourage its use.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
-rw-r--r-- | fdtdump.c | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -183,6 +183,11 @@ int main(int argc, char *argv[]) bool scan = false; off_t len; + fprintf(stderr, "\n" +"**** fdtdump is a low-level debugging tool, not meant for general use.\n" +"**** If you want to decompile a dtb, you probably want\n" +"**** dtc -I dtb -O dts <filename>\n\n" + ); while ((opt = util_getopt_long()) != EOF) { switch (opt) { case_USAGE_COMMON_FLAGS |