From: Jon Loeliger <jdl@freescale.com>
To: marty <leisner@rochester.rr.com>
Cc: "linuxppc-embedded@ozlabs.org" <linuxppc-embedded@ozlabs.org>
Subject: Re: version control for dts/dtb?
Date: Fri, 22 Jun 2007 12:24:55 -0500 [thread overview]
Message-ID: <1182533095.29873.30.camel@ld0161-tx32> (raw)
In-Reply-To: <000301c7b03e$0e2a42a0$9700a8c0@hplaptop>
On Sat, 2007-06-16 at 12:44, marty wrote:
> Is there a wy to figure out the version of the dtb file I'm using?
> At a minimum, it would be useful to have a node with the conversion time
> stuck somewhere...
>
> I ran dtc to convert binary to source, but that isn't necessarily what I
> wanted to look at -- just a single date
> code would be sufficient...
>
> marty
There is currently no direct version stamp in the
DTS or DTB files. You may be able to derive some
knowledge by running a DTB file through the DTC
with the input file as "dtb" and looking at an
output file of DTS, though. That is, "-I dtb -O dts"
and looking at it.
HTH,
jdl
next prev parent reply other threads:[~2007-06-22 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 17:44 version control for dts/dtb? marty
2007-06-22 17:24 ` Jon Loeliger [this message]
2007-06-22 18:08 ` Leisner, Martin
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=1182533095.29873.30.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=leisner@rochester.rr.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).