summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2009-09-02 13:43:56 +0000
committerCarl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>2009-09-02 13:43:56 +0000
commit9246ff40631a619579e563b65c80ff353cb33e46 (patch)
treefb1a6a524d5674f010a8044c036539a47604272f
parent84395ed69f290555e12e7256007eaf9a762762ff (diff)
downloadast2050-flashrom-9246ff40631a619579e563b65c80ff353cb33e46.zip
ast2050-flashrom-9246ff40631a619579e563b65c80ff353cb33e46.tar.gz
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. Corresponding to flashrom svn r708. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> Acked-by: Uwe Hermann <uwe@hermann-uwe.de>
-rw-r--r--internal.c6
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)
OpenPOWER on IntegriCloud