From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Different Port for TFTP communication
Date: Mon, 07 Apr 2014 18:52:43 +0200 [thread overview]
Message-ID: <20140407165243.3B074380958@gemini.denx.de> (raw)
In-Reply-To: <F50CAB352C149543A6F2FFE37D4B59348AC9E60A@S1.mackware.local>
Dear Mario,
In message <F50CAB352C149543A6F2FFE37D4B59348AC9E60A@S1.mackware.local> you wrote:
>
> I have a short question about TFTP usage in u-boot.
> Is it possible to change the Port for TFTP communication
> while u-boot is running. Standard path for TFTP is 69
> an let's say, we want to change port to 1500.
As is, this cannot be changed. The TFTP port number is hard wired
in the code - see "net/tftp.c":
...
18 /* Well known TFTP port # */
19 #define WELL_KNOWN_PORT 69
...
Of course it should be trivial to add a config option for this, or
even make it changable at runtime. But I have to admit that I don't
see many actual use cases for such a modification.
Could you please explain why you need to do this - is this just some
exotic environment, or is this needed for some more general use case?
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
For those who like this sort of thing, this is the sort of thing they
like. - Abraham Lincoln
next prev parent reply other threads:[~2014-04-07 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 13:32 [U-Boot] Different Port for TFTP communication Mario Albrecht
2014-04-07 16:52 ` Wolfgang Denk [this message]
2014-04-08 10:06 ` Wolfgang Denk
[not found] <mailman.9.1396951203.11170.u-boot@lists.denx.de>
2014-04-08 22:55 ` Nikolay Dimitrov
[not found] <mailman.7.1397037601.3278.u-boot@lists.denx.de>
2014-04-09 18:58 ` Nikolay Dimitrov
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=20140407165243.3B074380958@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