From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] distro_bootcmd: do not try to fetch unused bootfile for PXE
Date: Thu, 3 Dec 2015 10:09:50 -0700 [thread overview]
Message-ID: <5660775E.5050501@wwwdotorg.org> (raw)
In-Reply-To: <1449098137-7529-1-git-send-email-stefan.bruens@rwth-aachen.de>
On 12/02/2015 04:15 PM, Stefan Br?ns wrote:
> pxe get derives the pxelinux config file name from the bootfile name,
> but the bootfile itself is never used and might not even exist.
> Disable bootfile autoload to avoid the delay.
I wasn't CC'd on this and only accidentally noticed it, since it just
happened to be the first email in this list folder this morning. It's
good to CC people based on ./scripts/get_maintainer.pl's output.
> diff --git a/include/config_distro_bootcmd.h b/include/config_distro_bootcmd.h
> #define BOOTENV_DEV_PXE(devtypeu, devtypel, instance) \
> "bootcmd_pxe=" \
> BOOTENV_RUN_USB_INIT \
> - "dhcp; " \
> + "env exists autoload && setenv autoload_save ${autoload}; " \
> + "setenv autoload no; dhcp; " \
> + "env exists autoload_save && setenv autoload ${autoload_save}; " \
I think that last line should be unconditional; the previous statement
unconditionally sets autoload to no, so we want to unconditionally
restore the previous value of autoload, irrespective of whether it was
set or not.
I'd expect:
setenv autoload_save $autoload
setenv autoload no
dhcp
setenv autoload $autoload_save
setenv autoload_save
(or a cmdline option to "dhcp" to force it to only acquire an IP address
would be nice too).
prev parent reply other threads:[~2015-12-03 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 23:15 [U-Boot] [PATCH] distro_bootcmd: do not try to fetch unused bootfile for PXE Stefan Brüns
2015-12-03 17:09 ` Stephen Warren [this message]
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=5660775E.5050501@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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