Device tree flattening code not copying properties from blob

[Grant Likely]

On Thu, Jun 13, 2013 at 11:49 PM, Collins, Rod
<Rod.Collins at saabsensis.com> wrote:
> Grant
>
> What is considered the correct way to include the blob in the build so
> that it is not removed?

Don't put it in an __init section.  :-p

However, I realized that the .dtb.S target does exactly that under the
assumption that multiple blobs may be linked into the kernel, but only
one actually used. The correct thing to do in your case is indeed copy
the blob at boot.

Actually, the best thing to do is to not link the dtb into the kernel
at all. Either append it as another payload or pass it in via the
bootloader and make the kernel mark the dtb memory as reserved.
Statically linking into the kernel proper means the kernel needs to be
rebuilt for each and every target which neuters one of the reasons for
using device tree in the first place.

g.