Skip to contentSkip to conversation

of: add some debugging statements if initrd isn't found

PATCH New Andres Salomon 1 participant 1 message Feb 3, 2012 Device tree

lore
Share & tools
lore

Andres Salomon

author
#0 lore raw

PATCH 1/1 of: add some debugging statements if initrd isn't found

While debugging initrd problems in a FDT blob, it's nice to both terminate the "Looking for initrd properties... " with a newline, as well as letting us know which property wasn't found.

Signed-off-by Andres Salomon <[email protected]>
---
 drivers/of/fdt.c |    8 ++++++--
 1 files changed, 6 insertions(+), 2 deletions(-)
drivers/of/fdt.c +6 -2
index ea2bd1b..92234f7 100644
@@ -561,13 +561,17 @@ void __init early_init_dt_check_for_initrd(unsigned long node)
 	pr_debug("Looking for initrd properties... ");
 
 	prop = of_get_flat_dt_prop(node, "linux,initrd-start", &len);
-	if (!prop)
+	if (!prop) {
+		pr_debug("couldn't find linux,initrd-start\n");
 		return;
+	}
 	start = of_read_ulong(prop, len/4);
 
 	prop = of_get_flat_dt_prop(node, "linux,initrd-end", &len);
-	if (!prop)
+	if (!prop) {
+		pr_debug("couldn't find linux,initrd-end\n");
 		return;
+	}
 	end = of_read_ulong(prop, len/4);
 
 	early_init_dt_setup_initrd_arch(start, end);
Signature · 1 line
1.7.2.5