-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi.
I think it should be handled in mtd, rewriting the complete image only because a single block had a transient erase problem is a bit excessive imo. It also means that sysupgrade would loop forever in case of a really fatal issue, like when the image is too large for the given mtd partition. I'd say the mtd util should perform 3-5 consecutive tries in case of a block erase problem and then finally exit with a non zero code to notify the caller about the problem. The exit code could convey the nature of the problem, e.g. erase issue or mtd too short; this would allow sysupgrade to take appropriate actions without brute-forcing the flash into death. ~ Jow -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk9JErwACgkQdputYINPTPNlFgCeNaKCXiYIC+jxf2WhGxl7vAG8 988AnAzsUbpU14L5cXIBa3ESqSt3ymns =ouxM -----END PGP SIGNATURE----- _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
