From: Pavel Bartusek <pba@sysgo.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] bootretry enviroment variable
Date: Thu, 27 Nov 2003 19:45:28 +0100 [thread overview]
Message-ID: <3FC64648.2040905@sysgo.com> (raw)
Hi,
paste from the doc/README.autoboot
CONFIG_BOOT_RETRY_TIME
CONFIG_BOOT_RETRY_MIN
bootretry environment variable
These options determine what happens after autoboot is
stopped and U-Boot is waiting for commands.
CONFIG_BOOT_RETRY_TIME must be defined to enable the boot
retry feature. If the environment variable 'bootretry' is
found then its value is used, otherwise the retry timeout is
CONFIG_BOOT_RETRY_TIME. CONFIG_BOOT_RETRY_MIN is optional and
defaults to CONFIG_BOOT_RETRY_TIME. All times are in seconds.
If the retry timeout is negative, the U-Boot command prompt
never times out. Otherwise it is forced to be at least
CONFIG_BOOT_RETRY_MIN seconds. If no valid U-Boot command is
entered before the specified time the boot delay sequence is
restarted. Each command that U-Boot executes restarts the
timeout.
end of paste from the doc/README.autoboot
Currently is used function simple_strtoul() for parsing the bootretry
enviroment variable. It fails if the bootretry is negative. The attached
patch should fix it.
--
Pavel Bartusek <pba@sysgo.com>
Software Engineering
SYSGO Real-Time Solutions AG | Embedded and Real-Time Software
Lise-Meitner-Str.15
89081 Ulm, Germany
Voice: +49-731-9533-1295
FAX: +49-731-94683-10
www.sysgo.com | www.elinos.com | www.osek.de
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: bootretry.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20031127/524eac8d/attachment.txt
reply other threads:[~2003-11-27 18:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3FC64648.2040905@sysgo.com \
--to=pba@sysgo.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.