From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Cc: linuxppc-dev@ozlabs.org, "David H. Lynch Jr." <dhlii@dlasys.net>
Subject: Re: device trees.
Date: Mon, 11 May 2009 23:30:22 -0600 [thread overview]
Message-ID: <fa686aa40905112230ve176b30o25abcdf5c203f6c7@mail.gmail.com> (raw)
In-Reply-To: <20090512042733.8D4A21400054@mail184-dub.bigfish.com>
On Mon, May 11, 2009 at 10:27 PM, Stephen Neuendorffer
<stephen.neuendorffer@xilinx.com> wrote:
>> > OK, so the key question seems to be *when* the bitstream is
> associated
>> > with the
>> > device tree. =A0If at bitstream generation time, you can prepend the
> .dtb
>> > to the bitstream. =A0As long as the dtb doesn't contain the magic
>> > bitstream start code, you can go back and access it later.
>> >
>> You really mean prepend ? I was presuming that things would work
> better
>> if it was appended ?
>
> Yes, actually prepend is simpler because you don't have to know the size
> of the bitstream.
> Everything before the SYNC code in the bitstream is ignored.
...In this case, might need to preprocess the .dtb the escape out the
possibility of a sync code appearing.
g.
--=20
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-05-12 5:30 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 16:03 device trees David H. Lynch Jr.
2009-05-08 17:15 ` Timur Tabi
2009-05-08 18:43 ` Kumar Gala
2009-05-09 20:51 ` Grant Likely
2009-05-11 2:00 ` Michael Ellerman
2009-05-11 4:08 ` Grant Likely
2009-05-11 6:32 ` David H. Lynch Jr.
2009-05-11 13:51 ` Grant Likely
2009-05-11 15:52 ` Stephen Neuendorffer
2009-05-11 16:58 ` David H. Lynch Jr.
[not found] ` <20090511183638.F07C01438054@mail184-wa4.bigfish.com>
[not found] ` <4A08C599.2030100@dlasys.net>
[not found] ` <20090512005554.EEE1019D009B@mail129-dub.bigfish.com>
2009-05-12 2:34 ` David H. Lynch Jr.
2009-05-12 4:27 ` Stephen Neuendorffer
2009-05-12 5:30 ` Grant Likely [this message]
2009-05-13 0:10 ` Stephen Neuendorffer
2009-05-13 2:36 ` David Gibson
2009-05-13 4:03 ` Grant Likely
2009-05-13 6:11 ` David H. Lynch Jr.
2009-05-13 6:21 ` David Gibson
2009-05-13 18:11 ` David H. Lynch Jr.
2009-05-14 3:08 ` David Gibson
2009-05-14 12:51 ` David H. Lynch Jr.
2009-05-13 6:58 ` Stephen Neuendorffer
2009-05-11 16:45 ` David H. Lynch Jr.
2009-05-11 17:47 ` Grant Likely
2009-05-11 21:38 ` David H. Lynch Jr.
2009-05-11 22:29 ` Benjamin Herrenschmidt
2009-05-11 22:56 ` David Gibson
2009-05-12 2:37 ` Michael Ellerman
2009-05-11 23:09 ` Grant Likely
2009-05-12 1:12 ` David Gibson
2009-05-12 5:22 ` Grant Likely
2009-05-12 23:24 ` David Gibson
2009-05-13 0:01 ` Grant Likely
2009-05-13 0:13 ` David H. Lynch Jr.
2009-05-13 1:15 ` Grant Likely
2009-05-13 2:32 ` David Gibson
2009-05-11 23:19 ` Stephen Neuendorffer
2009-05-12 0:04 ` Grant Likely
2009-05-12 7:38 ` Wolfram Sang
2009-05-11 14:58 ` Timur Tabi
2009-05-11 16:54 ` David H. Lynch Jr.
2009-05-11 23:27 ` David Gibson
2009-05-11 22:25 ` Benjamin Herrenschmidt
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=fa686aa40905112230ve176b30o25abcdf5c203f6c7@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dhlii@dlasys.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=stephen.neuendorffer@xilinx.com \
/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).