Don't abort if chipset init failed because the failing init may have

been a warning only.
Even a failing chipset init (maybe due to unknown chipset) could still
get us reasonable probe results or at least forced reads.

Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Acked-by: Uwe Hermann <uwe@hermann-uwe.de>


git-svn-id: https://code.coreboot.org/svn/flashrom/trunk@708 2b7e53f0-3cfb-0310-b3e9-8179ed1497e1

1 files changed, 5 insertions, 1 deletions

diff --git a/internal.c b/internal.c
index 3e3808e..a3b2ae5 100644
--- a/internal.c
+++ b/internal.c
@@ -130,7 +130,11 @@ int internal_init(void)
 
 	board_flash_enable(lb_vendor, lb_part);
 
-	return ret; 
+	/* Even if chipset init returns an error code, we don't want to abort.
+	 * The error code might have been a warning only.
+	 * Besides that, we don't check the board enable return code either.
+	 */
+	return 0; 
 }
 
 int internal_shutdown(void)