linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* version control for dts/dtb?
@ 2007-06-16 17:44 marty
  2007-06-22 17:24 ` Jon Loeliger
  0 siblings, 1 reply; 3+ messages in thread
From: marty @ 2007-06-16 17:44 UTC (permalink / raw)
  To: linuxppc-embedded

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: version control for dts/dtb?
  2007-06-16 17:44 version control for dts/dtb? marty
@ 2007-06-22 17:24 ` Jon Loeliger
  2007-06-22 18:08   ` Leisner, Martin
  0 siblings, 1 reply; 3+ messages in thread
From: Jon Loeliger @ 2007-06-22 17:24 UTC (permalink / raw)
  To: marty; +Cc: linuxppc-embedded@ozlabs.org

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* RE: version control for dts/dtb?
  2007-06-22 17:24 ` Jon Loeliger
@ 2007-06-22 18:08   ` Leisner, Martin
  0 siblings, 0 replies; 3+ messages in thread
From: Leisner, Martin @ 2007-06-22 18:08 UTC (permalink / raw)
  To: Jon Loeliger, marty; +Cc: Lund, Nathan, linuxppc-embedded

I made a node "revision" which was tied into rcs...

 ...
        compatible =3D "mpc74xx";
        revision =3D "$Revision: 1.7 $";
        #address-cells =3D <1>;
        #size-cells =3D <1>;
        linux,phandle =3D <100>;
...

This seems to do what I wanted, I can then see in /proc/device-tree what
dts I'm running...

marty
> -----Original Message-----
> From:=20
> linuxppc-embedded-bounces+martin.leisner=3Dxerox.com@ozlabs.org=20
> [mailto:linuxppc-embedded-bounces+martin.leisner=3Dxerox.com@ozl
> abs.org] On Behalf Of Jon Loeliger
> Sent: Friday, June 22, 2007 1:25 PM
> To: marty
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: version control for dts/dtb?
>=20
> 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=20
> conversion time=20
> > stuck somewhere...
> >=20
> > I ran dtc to convert binary to source, but that isn't=20
> necessarily what I=20
> > wanted to look at -- just a single date
> > code would be sufficient...
> >=20
> > marty
>=20
>=20
> 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.
>=20
> HTH,
> jdl
>=20
>=20
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-06-22 18:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-16 17:44 version control for dts/dtb? marty
2007-06-22 17:24 ` Jon Loeliger
2007-06-22 18:08   ` Leisner, Martin

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).