Don't abort if chipset init failed because the failing init may have been a warning only. This was requested by Stefan.
Signed-off-by: Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Index: flashrom-internal_init_noabort/internal.c =================================================================== --- flashrom-internal_init_noabort/internal.c (Revision 706) +++ flashrom-internal_init_noabort/internal.c (Arbeitskopie) @@ -130,7 +130,11 @@
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)
On 02.09.2009 00:53, Carl-Daniel Hailfinger wrote:
Don't abort if chipset init failed because the failing init may have been a warning only. This was requested by Stefan.
At least I think it was requested by Stefan ~2 months ago with the reason that even a failing chipset init (maybe due to unknown chipset) could still get us reasonable probe results or at least forced reads. Apologies if I misremembered something.
Regards, Carl-Daniel
On Wed, Sep 02, 2009 at 12:53:25AM +0200, Carl-Daniel Hailfinger wrote:
Don't abort if chipset init failed because the failing init may have been a warning only. This was requested by Stefan.
Signed-off-by: Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Acked-by: Uwe Hermann uwe@hermann-uwe.de
Uwe.
On 02.09.2009 15:29, Uwe Hermann wrote:
On Wed, Sep 02, 2009 at 12:53:25AM +0200, Carl-Daniel Hailfinger wrote:
Don't abort if chipset init failed because the failing init may have been a warning only. This was requested by Stefan.
Signed-off-by: Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net
Acked-by: Uwe Hermann uwe@hermann-uwe.de
Thanks, r708.
Regards, Carl-Daniel