[U-Boot] 4K padding of ARM DT blob
Masahiro Yamada
yamada.masahiro at socionext.com
Thu Mar 12 10:50:07 CET 2015
Hi.
2015-03-12 17:58 GMT+09:00 Yehuda Yitschak <yehuday at 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 ?
Yes, depending on when you modify the FDT.
In Driver Model, most of drivers refer to the FDT when probing.
(The offset address is stored in the "of_offset" member of struct udevice.)
The scenario of our trouble is like this:
[1] Devices are bound by dm_init_and_scan().
(udevice->of_offset is set)
[2] The FDT is modified.
(The offset address to each node changes.)
[3] Some devices are probed
(udevice->of_offset is referred, but the expected node is not there!)
I guess you can modify the FDT before [1] or after[3].
Simon,
What do you think?
--
Best Regards
Masahiro Yamada
More information about the U-Boot
mailing list