Another possibility is to pad the DTB with a DESYNC command and the correct pad frame, just in case it cannot be prevented.
Steve > -----Original Message----- > From: Grant Likely [mailto:grant.lik...@secretlab.ca] > Sent: Monday, May 11, 2009 10:30 PM > To: Stephen Neuendorffer > Cc: David H. Lynch Jr.; linuxppc-dev@ozlabs.org > Subject: Re: device trees. > > On Mon, May 11, 2009 at 10:27 PM, Stephen Neuendorffer > <stephen.neuendorf...@xilinx.com> wrote: > >> > OK, so the key question seems to be *when* the bitstream is > > associated > >> > with the > >> > device tree. If at bitstream generation time, you can prepend the > > .dtb > >> > to the bitstream. As 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. > > -- > Grant Likely, B.Sc., P.Eng. > Secret Lab Technologies Ltd. This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately. _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
