On Tue, Sep 02, 2008 at 06:14:38PM -0600, Gary Thomas wrote: > David Gibson wrote: >> On Tue, Sep 02, 2008 at 03:56:30PM -0600, Gary Thomas wrote: > <snip> >>> What gives? Why is explicit hex sometimes an error and sometimes not? >> >> Because we changed the format at one point. Originally (the "dts-v0" >> format) it was implicitly hex everywhere, which turned out to be a >> mistake. So we introduced the new dts-v1 format which uses C-style >> literals. New-style files are marked with a /dts-v1/; token at the >> top of the file. > > Gotcha, thanks. Not sure where I picked up the dts-v0 file I based > my platform on, but at least now I understand the magic.
Well, it's only fairly recently that we converted all the in-kernel files to v1, so you may have grabbed something before the conversion. We're hoping to get everyone converted over to v1 as quickly as possible, to avoid this sort of confusion. >>> Is the format of this file documented anywhere (I've not found it)? >> >> It's in Documentation/dts-format.txt in the dtc tree. I don't think >> that's been included in the version of dtc in the kernel tree, though, >> so you'll need to download the standalone dtc. >> > > Where do I find this "dtc" tree? git://git.jdl.com/software/dtc.git Or get tarballs from http://jdl.com/software/ -- 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 _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
