diff options
| author | Simon Glass <sjg@chromium.org> | 2021-12-16 20:59:34 -0700 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2021-12-23 10:24:40 -0500 |
| commit | ff66e7bb73233a4decfcdb66b7a858399dbccf50 (patch) | |
| tree | 130deb1f3ddb5d1436e8fc57ff4fe8e98068dd1f /cmd | |
| parent | 39605c6ec3618a848a4a1c4063d474270deab442 (diff) | |
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 'cmd')
| -rw-r--r-- | cmd/bdinfo.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/cmd/bdinfo.c b/cmd/bdinfo.c index bf63cc6d64..c56b3f4f6e 100644 --- a/cmd/bdinfo.c +++ b/cmd/bdinfo.c @@ -128,6 +128,8 @@ int do_bdinfo(struct cmd_tbl *cmdtp, int flag, int argc, char *const argv[]) lmb_init_and_reserve(&lmb, gd->bd, (void *)gd->fdt_blob); lmb_dump_all_force(&lmb); + if (IS_ENABLED(CONFIG_OF_REAL)) + printf("devicetree = %s\n", fdtdec_get_srcname()); } arch_print_bdinfo(); |