aboutsummaryrefslogtreecommitdiff
path: root/lib/dhry
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2021-12-16 20:59:34 -0700
committerTom Rini <trini@konsulko.com>2021-12-23 10:24:40 -0500
commitff66e7bb73233a4decfcdb66b7a858399dbccf50 (patch)
tree130deb1f3ddb5d1436e8fc57ff4fe8e98068dd1f /lib/dhry
parent39605c6ec3618a848a4a1c4063d474270deab442 (diff)
downloadu-boot-ff66e7bb73233a4decfcdb66b7a858399dbccf50.zip
u-boot-ff66e7bb73233a4decfcdb66b7a858399dbccf50.tar.gz
u-boot-ff66e7bb73233a4decfcdb66b7a858399dbccf50.tar.bz2
fdt: Report the devicetree source
It can be confusing to figure out where the devicetree came from. It seems important enough to warrant a message during boot. Add information about the number of devices and uclasses too since it is helpful to have some idea what is going on with driver model. Report the devicetree source in bdinfo too. This looks something like this, with > marking the new line. U-Boot 2021.10-00190 (Oct 30 2021 - 09:01:29 -0600) DRAM: 128 MiB > Core: 42 devices, 11 uclasses, devicetree: passage Flash: 64 MiB Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'lib/dhry')
0 files changed, 0 insertions, 0 deletions