From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add separate environment variable for tftp server
Date: Thu, 28 Mar 2013 18:20:55 -0400 [thread overview]
Message-ID: <5154C247.2020109@ti.com> (raw)
In-Reply-To: <5154BD18.8000605@ooma.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 03/28/2013 05:58 PM, Rory Toma wrote:
> This patch uses the environment variable "tftpserverip" as the
> tftp server IP instead of serverip. If it is unset, it defaults to
> serverip.
What's the use case for this exactly? I believe serverip is set based
on the next-server param, if applicable from the DHCP request already
(Joe?). In terms of scripting you can today just do 'tftp ${loadaddr}
${mytfpserver}:${bootfile}'. Thanks!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRVMJHAAoJENk4IS6UOR1WlMoQAIpQ4WzJoJO/wIvsJ66arF0q
mvhrA1tJer0ZnXfDF2Lp3SHDyQtYEPQcjxgsA+zn21AB9aOHJVEWPxonrOzQpa79
mghOa2xJUm/Yjr/mS7qphQpwk9n8oaGemZrK8mF/5HR0NGEMnW9s4j0hErNpM1Vc
dPNZ+aA0JmJ5p1QQDscFMhQZefJ9tlyvFX315IpF5v7FU7ecHrVsEo034Dgh2Xo6
nI83xWLSeWTEbTttRCN89Auwr8kzQGQ+eAp3qAWqKv3QSbmV6uGwqlKBixgd/9rm
vXdC5tq9rkkyTUo4tHLSyJi+sKkYqB98a2Q6onffuqthAypNQvzAnlwOu4wvWPRL
JJsXdWVHl8rxexCKc88ppBdaEzLjQOsfQFU03RM37nAKFLt4XdUIWukOL6PE+yex
PPlLAPswcQIF5rzdqhk7dBt5DP67oDnnnKiTy/ZTSyUNjhdra/1CNRwM0eYBBtrP
m+/XWqRO9Le7Z/VDwBzTJ8N+4j3ieZ/yRnPbN9pyLRM+vKFJwEOLs/a+2/Q3K75i
7eOqZORAw7EERLsMzd8NyC3aCWFFadCWwrxjIUsgdWfhSLr0a5gAWImx8Mg1JgQj
5DSOoodgpgsRQ0eNCGNNip4ULZX7E5wzDAnj3WcI15OTsCz6UYax3CTwD+ngNQfb
0e/Vr5UDz+g0sjbM+g1s
=SQ6Q
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2013-03-28 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 21:58 [U-Boot] [PATCH] Add separate environment variable for tftp server Rory Toma
2013-03-28 22:20 ` Tom Rini [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=5154C247.2020109@ti.com \
--to=trini@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox