From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Matt Sealey <matt-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
Cc: u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org,
devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
Jerry Van Baren <gerald.vanbaren-JJi787mZWgc@public.gmane.org>
Subject: Re: [U-Boot] dtc/u-boot tool naming, "ftdump", "mkimage"
Date: Thu, 15 Jan 2009 11:49:19 +1100 [thread overview]
Message-ID: <20090115004919.GA26726@yookeroo.seuss> (raw)
In-Reply-To: <496E849A.8020707-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
On Wed, Jan 14, 2009 at 06:34:34PM -0600, Matt Sealey wrote:
> Josh Boyer wrote:
>
>> David has said before that ftdump is sort of a pointless debugging tool.
>> Or at least that is what the Debian bug report referrenced as the reason
>> from removing it from the Debian dtc package.
>
> As long as you have the original device tree source code to hand. I tend
> to find that the guy who sent me the device tree and kernel for me to
> test, has gone to bed and will not be back for 8 to 10 hours. Rather
> than hang around, on the event that I think it's a device tree problem I
> tend to ftdump to see what's going on.
Like I said, "dtc -I dtb -O dts" is the non-hacky way to do this.
--
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
prev parent reply other threads:[~2009-01-15 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 17:57 dtc/u-boot tool naming, "ftdump", "mkimage" Matt Sealey
2009-01-14 18:10 ` Josh Boyer
2009-01-14 18:59 ` Matt Sealey
2009-01-14 19:11 ` Jerry Van Baren
2009-01-14 19:19 ` Josh Boyer
[not found] ` <20090114191905.GA18581-JVa43G0qJ78RlTYtMZUE4cJ8OCA1ciLf@public.gmane.org>
2009-01-14 22:22 ` [U-Boot] " David Gibson
2009-01-15 0:34 ` Matt Sealey
[not found] ` <496E849A.8020707-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
2009-01-15 0:49 ` David Gibson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090115004919.GA26726@yookeroo.seuss \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
--cc=gerald.vanbaren-JJi787mZWgc@public.gmane.org \
--cc=matt-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org \
--cc=u-boot-0aAXYlwwYIKGBzrmiIFOJg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox