From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 6/6] fdt: Add a Linux tool for reading values from FDT files
Date: Mon, 20 Aug 2012 23:51:55 -0400 [thread overview]
Message-ID: <201208202351.56466.vapier@gentoo.org> (raw)
In-Reply-To: <CANr=Z=aPMG-BXZ4KQB-W4V2p_Fsw6OFyXPFUADNTcTauypcR=g@mail.gmail.com>
On Monday 20 August 2012 20:51:32 Joe Hershberger wrote:
> On Mon, Aug 20, 2012 at 7:24 PM, Mike Frysinger wrote:
> > On Monday 20 August 2012 19:40:45 Joe Hershberger wrote:
> >> On Fri, Aug 17, 2012 at 6:35 PM, Mike Frysinger wrote:
> >> > On Friday 17 August 2012 16:34:40 Joe Hershberger wrote:
> >> >> Designed to be able to access itb files on a filesystem or an mtd
> >> >> partition.
> >> >>
> >> >> Supports print and list (like the fdt command) and also offset for
> >> >> finding the offset and size of a given property in an FDT file.
> >> >>
> >> >> This is especially helpful when reading properties from an ITB file.
> >> >
> >> > doesn't the ftdump utility from the dtc package cover your needs ?
> >>
> >> No. The purpose is to use this utility e.g. in a Linux shell script
> >> to retrieve a property from the ITB. The two places I use it are to
> >> retrieve a version number from the ITB and to identify the offset and
> >> size of a data block (image) in the ITB.
> >>
> >> From what I can see the ftdump utility in the dtc component just dumps
> >> the ITB as a single blob with no options. I'm looking at the dtc
> >> 1.2.0 source.
> >
> > ... so wouldn't the logical thing be to extend ftdump to support your
> > needs and send a patch to the DTC authors rather than to write an entire
> > tool from scratch and commit it to a tree that is merely a user of
> > device trees ?
>
> Yes it probably would have been, if I had noticed that the ftdump
> utility existed, then that is the approach I would have taken. I
> think it is of specific use to u-boot users, but if you think it's
> better to extend ftdump, I guess I could take that approach.
i think it has a better chance of being maintained and other people using it
if it were merged into the canonical DTC project. i can see a more swiss army
type tool being useful to people rather than having to pipe it all through
awk.
git: git://git.jdl.com/software/dtc.git
e-mail: devicetree-discuss at lists.ozlabs.org
they're friendly people :)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120820/e98301c9/attachment.pgp>
next prev parent reply other threads:[~2012-08-21 3:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 20:34 [U-Boot] [PATCH 1/6] fdt: Check error codes returned from fdtlib when loading ITB Joe Hershberger
2012-08-17 20:34 ` [U-Boot] [PATCH 2/6] fdt: Limit printed hex in fdt print and list commands Joe Hershberger
2012-10-25 20:59 ` [U-Boot] [U-Boot, " Tom Rini
2012-10-29 0:54 ` Jerry Van Baren
2012-08-17 20:34 ` [U-Boot] [PATCH 3/6] fdt: Add get commands to fdt Joe Hershberger
2012-10-25 21:08 ` [U-Boot] [U-Boot,3/6] " Tom Rini
2012-08-17 20:34 ` [U-Boot] [PATCH 4/6] fdt: Identify scripts in ITBs as printable strings Joe Hershberger
2012-08-17 20:34 ` [U-Boot] [PATCH 5/6] fdt: Check for a token to skip auto-hash validation Joe Hershberger
2012-08-17 20:34 ` [U-Boot] [PATCH 6/6] fdt: Add a Linux tool for reading values from FDT files Joe Hershberger
2012-08-17 23:35 ` Mike Frysinger
2012-08-20 23:40 ` Joe Hershberger
2012-08-21 0:24 ` Mike Frysinger
2012-08-21 0:51 ` Joe Hershberger
2012-08-21 3:51 ` Mike Frysinger [this message]
2012-09-23 23:06 ` Marek Vasut
2012-10-04 17:38 ` [U-Boot] [PATCH 1/6] fdt: Check error codes returned from fdtlib when loading ITB Joe Hershberger
2012-10-08 23:45 ` Jerry Van Baren
2012-10-08 23:51 ` Tom Rini
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=201208202351.56466.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox