From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Patch: allow a fixed port for TFTP
Date: Tue, 11 Jan 2005 10:08:16 -0500 [thread overview]
Message-ID: <41E3EBE0.3070909@smiths-aerospace.com> (raw)
In-Reply-To: <41E3074A.9040703@orkun.us>
Tolunay Orkun wrote:
> Jerry,
>
> I have expressed my view that this patch does not address a real
> problem. You mentioned that all these modifications were necessary
> because the user were unable to configure their computer (lack of
> necessary skills or lack of administrative access to configure Windows
> firewall).
>
> Nevertheless, if Wolfgang approves it, I would prefer changes to the
> name of environment variable you are using. When referring to TCP/IP
> services, we normally associate ports with the port the server component
> is listening. Thus "tftpport" is not clear enough and may mislead people
> to the server port. I would prefer more verbose "tftpclientport" or
> "tftpsrcport". This would allow us to define "tftpserverport" or
> "tftpdestport" later if necessary as well.
>
> I do not object to CONFIG_TFTP_PORT, since same variable could be use to
> enable configurable client and server ports if tftpserverport were to be
> defined. In fact, I would include support for server port environment
> support now since it would make your match more useful for a larger
> audience IMHO.
>
> Best regards,
> Tolunay
>
> Jerry Van Baren wrote:
>
>> Hi Wolfgang, try two on the patch attached.
>>
>> * Patch by Jerry Van Baren 10 January 2005
>> - Add a configuration option CONFIG_TFTP_PORT and optional env
>> variable tftpport to force TFTP to use a fixed UDP port.
>>
>> gvb
I kind of like tftpclientport, that is much more descriptive. Thanks
for the suggestion. I've rolled Yet Another Patch[tm].
gvb
next prev parent reply other threads:[~2005-01-11 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 17:09 [U-Boot-Users] Patch: allow a fixed port for TFTP Jerry Van Baren
2005-01-10 22:52 ` Tolunay Orkun
2005-01-11 15:08 ` Jerry Van Baren [this message]
2005-01-11 22:46 ` Wolfgang Denk
2005-09-24 20:38 ` Wolfgang Denk
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=41E3EBE0.3070909@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.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