From: Matt Sealey <matt@genesi-usa.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: u-boot@lists.denx.de, devicetree-discuss@ozlabs.org
Subject: Re: dtc/u-boot tool naming, "ftdump", "mkimage"
Date: Wed, 14 Jan 2009 18:34:34 -0600 [thread overview]
Message-ID: <496E849A.8020707@genesi-usa.com> (raw)
In-Reply-To: <20090114191905.GA18581@yoda.jdub.homelinux.org>
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.
It might have some use somewhere someday, but yeah.. I guess.. bringing
it out from a build into a package is kind of a dumb idea.
> Maybe we should just remove it entirely if it's not really going to be
> maintained long-term.
Up to you.
-- Matt
WARNING: multiple messages have this Message-ID (diff)
From: Matt Sealey <matt@genesi-usa.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] dtc/u-boot tool naming, "ftdump", "mkimage"
Date: Wed, 14 Jan 2009 18:34:34 -0600 [thread overview]
Message-ID: <496E849A.8020707@genesi-usa.com> (raw)
In-Reply-To: <20090114191905.GA18581@yoda.jdub.homelinux.org>
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.
It might have some use somewhere someday, but yeah.. I guess.. bringing
it out from a build into a package is kind of a dumb idea.
> Maybe we should just remove it entirely if it's not really going to be
> maintained long-term.
Up to you.
-- Matt
next prev parent reply other threads:[~2009-01-15 0:34 UTC|newest]
Thread overview: 16+ 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 17:57 ` [U-Boot] " Matt Sealey
2009-01-14 18:10 ` Josh Boyer
2009-01-14 18:10 ` [U-Boot] " Josh Boyer
2009-01-14 18:59 ` Matt Sealey
2009-01-14 18:59 ` [U-Boot] " Matt Sealey
2009-01-14 19:11 ` Jerry Van Baren
2009-01-14 19:11 ` [U-Boot] " Jerry Van Baren
2009-01-14 19:19 ` Josh Boyer
2009-01-14 19:19 ` [U-Boot] " Josh Boyer
[not found] ` <20090114191905.GA18581-JVa43G0qJ78RlTYtMZUE4cJ8OCA1ciLf@public.gmane.org>
2009-01-14 22:22 ` David Gibson
2009-01-14 22:22 ` David Gibson
2009-01-15 0:34 ` Matt Sealey [this message]
2009-01-15 0:34 ` Matt Sealey
[not found] ` <496E849A.8020707-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org>
2009-01-15 0:49 ` David Gibson
2009-01-15 0:49 ` David Gibson
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=496E849A.8020707@genesi-usa.com \
--to=matt@genesi-usa.com \
--cc=devicetree-discuss@ozlabs.org \
--cc=jwboyer@gmail.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.