[U-Boot] 4K padding of ARM DT blob

[Yehuda Yitschak <yehuday@marvell.com>]

Thanks Masahiro 

Actually, I am considering to modify u-boot's own FDT to reflect changes in configurable boards like development boards.
So maybe the padding is good for my needs after all  :)

Do you see any issue with such an approach ?

Thanks

Yehuda 

> -----Original Message-----
> From: Masahiro Yamada [mailto:yamada.masahiro at socionext.com]
> Sent: Thursday, March 12, 2015 10:10
> To: Yehuda Yitschak
> Cc: Simon Glass; Tom Rini; Hanna Hawa; u-boot at lists.denx.de
> Subject: Re: [U-Boot] 4K padding of ARM DT blob
> 
> Hi.
> 
> 2015-03-12 15:46 GMT+09:00 Yehuda Yitschak <yehuday@marvell.com>:
> > Hey Simon
> >
> > Thanks for the clarification
> >
> > Just out of curiosity, how can the padding help modify the FDT in u-boot ?
> 
> If you insert a new node/property, or change a property for a longer value,
> the FDT blob will get longer.
> So, you need some extra space for modification.
> Otherwise, the U-Boot image will be overritten in case of
> CONFIG_OF_EMBED.
> 
> But, as Simon said, U-Boot never modifies a FDT that is used to configure U-
> Boot itself.
> 
> 
> Just in case, let me add a little more explanation:
> What is confusing is, U-Boot can modify a FDT that is passed to the kernel.
> U-Boot can have two different instances of FDTs: one for configuring U-Boot
> and the other for configuring Linux.
> We are talking about the former in this thread.
> 
> 
> 
> Best Regards
> Masahiro Yamada