In this very interesting post, http://beagleboard.org/discuss?place=topic%2Fbeagleboard%2FjnfNZIIC1V8%2Fdiscussion,
“… The Device Tree Binaries get appended to u-boot.img, luckly we really
don’t use them, as we just grab the kernel version…”
I don’t quite yet grasp the full extent of what this statement means…
Q) But do the current u-boot and/or SPL for BeagleBone/BeagleBoard scan the device tree to setup hardware for either both SPL/u-boot or is everything mainly done through the static functions in board.c?
I grepped on “CONFIG_OF_CONTROL” in my patched u-boot tree (2017.01 - patched a couple of months ago). This is set to “y” in the defconfig, but I couldn’t find any of the functions (e.g. sh_serial_ofdata_to_platdata) sandwiched within this define in u-boot.map, granted that was about the extent to which I looked.