From mboxrd@z Thu Jan 1 00:00:00 1970 From: Makito SHIOKAWA Date: Thu, 24 Apr 2008 18:59:05 +0900 Subject: [U-Boot-Users] [RFC] Implementing Boot Image Fallback on U-Boot In-Reply-To: <200804240700.36826.matthias.fuchs@esd-electronics.com> References: <480FF63C.2030407@miraclelinux.com> <200804240700.36826.matthias.fuchs@esd-electronics.com> Message-ID: <481059E9.5090302@miraclelinux.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, Thank you for your reply. > take a look at Wolfgang's last posting from Tuesday on the 'intended behavior > of bootm'. The bootlimit/altbootcmd function (in your case probably together > with a hardware watchdog) could be the stuff you are (and I was) looking for. This corresponds to CGL Availability Requirements Definition V4.0: AVL.9.1, whereas Boot Image Fallback is AVL.9.0. (http://developer.osdl.org/dev/cgl/cgl40/cgl40-availability.pdf) Boot Image Fallback must handle not only image CRC error before kernel boot, but a boot failure like kernel panic during kernel boot process (after image has successfully loaded). Also, it must fallback after power-on reset. -- MIRACLE LINUX CORPORATION Makito SHIOKAWA