From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC] Implementing Boot Image Fallback on U-Boot
Date: Thu, 24 Apr 2008 15:12:52 +0200 [thread overview]
Message-ID: <20080424131252.278D024AB1@gemini.denx.de> (raw)
In-Reply-To: Your message of "Thu, 24 Apr 2008 18:59:05 +0900." <481059E9.5090302@miraclelinux.com>
In message <481059E9.5090302@miraclelinux.com> you wrote:
>
> > 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.
Actually it implements the features needed to handle all of this.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Every revolutionary idea - in science, politics, art, or whatever -
evokes three stages of reaction in a hearer:
1. It is completely impossible - don't waste my time.
2. It is possible, but it is not worth doing.
3. I said it was a good idea all along.
next prev parent reply other threads:[~2008-04-24 13:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 2:53 [U-Boot-Users] [RFC] Implementing Boot Image Fallback on U-Boot Makito SHIOKAWA
2008-04-24 5:00 ` Matthias Fuchs
2008-04-24 9:59 ` Makito SHIOKAWA
2008-04-24 13:12 ` Wolfgang Denk [this message]
2008-04-24 9:01 ` Bartlomiej Sieka
2008-04-24 11:16 ` Makito SHIOKAWA
2008-04-24 12:42 ` Makito SHIOKAWA
2008-04-24 13:23 ` Wolfgang Denk
2008-04-25 10:45 ` Makito SHIOKAWA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080424131252.278D024AB1@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox