Look for both fdtaddr and fdt_addr env var names. Grepping the u-boot

source shows that board vendors seem to be about evenly split on this.

This commit is a trivial change to note that while the previous change
was supposed to be whitespace only, this functional change also crept in.
The added lines were:

  /* Board vendors use both fdtaddr and fdt_addr names.  Grrrr. */

  if (s == NULL)
	s = ub_env_get("fdt_addr");

1 files changed, 1 insertions, 1 deletions

diff --git a/sys/boot/fdt/fdt_loader_cmd.c b/sys/boot/fdt/fdt_loader_cmd.c
index 80acd8f..d8ad942 100644
--- a/sys/boot/fdt/fdt_loader_cmd.c
+++ b/sys/boot/fdt/fdt_loader_cmd.c
@@ -267,7 +267,7 @@ fdt_setup_fdtp()
 		return fdt_load_dtb_addr(fdt_to_load);
 	}
 
-	/* Board vendors use both fdtaddr and fdt_addr.  Grrrr. */
+	/* Board vendors use both fdtaddr and fdt_addr names.  Grrrr. */
 	s = ub_env_get("fdtaddr");
 	if (s == NULL)
 		s = ub_env_get("fdt_addr");