[U-Boot] [RFC PATCH 24/44] Revert "fdt- Tell the FDT library where the device tree is"

Simon Glass sjg at chromium.org
Sat Jan 5 02:51:53 CET 2013


This reverts commit 3b73459ea3421e9f8c6c8c62e1d3fe458ca5bc56.

In practice it doesn't seem like a good idea to make the the working
FDT point to the control FDT. Now that we can access the control FDT
using the 'fdt' command, there is no need for this feature. Remove it.

Signed-off-by: Simon Glass <sjg at chromium.org>
---
 common/main.c |    8 --------
 1 files changed, 0 insertions(+), 8 deletions(-)

diff --git a/common/main.c b/common/main.c
index 5d8454e..bbc3be6 100644
--- a/common/main.c
+++ b/common/main.c
@@ -45,10 +45,6 @@
 #include <fdtdec.h>
 #endif
 
-#ifdef CONFIG_OF_LIBFDT
-#include <fdt_support.h>
-#endif /* CONFIG_OF_LIBFDT */
-
 #include <post.h>
 #include <linux/ctype.h>
 #include <menu.h>
@@ -500,10 +496,6 @@ void main_loop (void)
 #endif /* CONFIG_MENUKEY */
 #endif /* CONFIG_BOOTDELAY */
 
-#if defined CONFIG_OF_CONTROL
-	set_working_fdt_addr((void *)gd->fdt_blob);
-#endif /* CONFIG_OF_CONTROL */
-
 	/*
 	 * Main Loop for Monitor Command Processing
 	 */
-- 
1.7.7.3



More information about the U-Boot mailing list