From 9246ff40631a619579e563b65c80ff353cb33e46 Mon Sep 17 00:00:00 2001 From: Carl-Daniel Hailfinger Date: Wed, 2 Sep 2009 13:43:56 +0000 Subject: 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 Acked-by: Uwe Hermann --- internal.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'internal.c') diff --git a/internal.c b/internal.c index 3e3808ec..a3b2ae5c 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) -- cgit v1.2.3