From: Gary Thomas <gary@mlbassoc•com>
To: Linuxppc-dev@ozlabs•org
Subject: Re: DTS question
Date: Tue, 02 Sep 2008 18:14:38 -0600 [thread overview]
Message-ID: <48BDD6EE.40600@mlbassoc.com> (raw)
In-Reply-To: <20080902234207.GB9681@yookeroo.seuss>
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.
>> 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?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2008-09-03 0:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 21:56 DTS question Gary Thomas
2008-09-02 23:42 ` David Gibson
2008-09-03 0:14 ` Gary Thomas [this message]
2008-09-03 0:25 ` David Gibson
2008-09-02 23:43 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2008-03-20 21:33 Sean MacLennan
2008-03-20 21:47 ` Segher Boessenkool
2008-03-20 21:48 ` Scott Wood
2008-03-20 22:19 ` Sean MacLennan
2008-03-20 22:26 ` Scott Wood
2008-03-21 4:12 ` Sean MacLennan
2008-03-21 4:34 ` Grant Likely
2008-03-21 5:09 ` Sean MacLennan
2008-03-21 7:05 ` David Gibson
2008-03-21 11:35 ` Segher Boessenkool
2008-03-25 22:12 ` David Gibson
2008-03-26 15:32 ` Segher Boessenkool
2008-03-26 23:40 ` David Gibson
2008-03-27 3:42 ` Sean MacLennan
2008-03-21 11:31 ` Segher Boessenkool
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=48BDD6EE.40600@mlbassoc.com \
--to=gary@mlbassoc$(echo .)com \
--cc=Linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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