public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 (take 3)
Date: Wed, 12 Jan 2005 08:40:58 -0500	[thread overview]
Message-ID: <41E528EA.8040906@smiths-aerospace.com> (raw)
In-Reply-To: <41E4DB2C.1010908@orkun.us>

Tolunay Orkun wrote:
> Wolfgang Denk wrote:
> 
>> In message <41E4657F.6010406@orkun.us> you wrote:
>>  
>>
>>> I will pledge for clarity over 6 more bytes in environment which most 
>>> boards will not define anyway. If that is not reasonable, please 
>>> allow for "tftpsrcport" or "tftpcport".
>>>   
>>
>>
>> So be it "tftpsrcport" then. Or "tftpsrcp" :-)
>>  
>>
> I prefer "tftpsrcport". I hope Jerry will agee as well.
> 
>> ["tftpcport" ??? TFT-PC-Port? Or 'c' like what???]
>>  
>>
> 'c' was to stand for "client". Just like bootpc and bootps in /etc/services
> 
>>> I actually want to provide a complimentary patch over this one to 
>>> make the tftp server port configurable which the environment variable 
>>> can be appropriately named as one of "tftpserverport", "tftpdestport" 
>>> or   
>>
>>
>> tftpdstport or tftpdstp, please.
>>  
>>
> IMHO, "tftpdstport" is better.
> 
>>> "tftpsport". I also want to use the same CONFIG_TFTP_PORT variable to   
>>
>>
>> [Seems to be some funny kind of exercise, this: TFTP  sport.  And  is
>> misleading - TFTP _S_ource Port ?]
>>  
>>
> 
> Yes, that is kind of vague. Again, I used bootpc and bootps analogy.
> 
>>> enable both environment variables unless you object in which case 
>>> naming the config variables as CONFIG_TFTP_CLIENT_PORT and 
>>> CONFIG_TFTP_SERVER_PORT is probably better.
>>>   
>>
>>
>> OK.
>>  
>>
> OK for which? OK to use CONFIG_TFTP_PORT for enabling code for both 
> "tftpsrcport" and "tftpdstport"?
> 
> Best regards,
> Tolunay

OK, If I follow all the quoting correctly :-O, an acceptable set of 
names is the following.  This is not Tolunay's first choice (sorry), in 
this case I'll suck up and side with Wolfgang ;-).

tftpsrcp - Source UDP port for TFTP (Jerry's patch)
tftpdstp - Destination UDP port for TFTP (Tolunay's projected
            follow-on)

Patch Version 4.rc1 to follow...

gvb
"There comes a time in the history of any project when it becomes 
necessary to shoot the engineers and begin production." (attributed to 
MacUser in 1990)

  reply	other threads:[~2005-01-12 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-11 15:11 [U-Boot-Users] Patch: allow a fixed port for TFTP (take 3) Jerry Van Baren
2005-01-11 22:49 ` Wolfgang Denk
2005-01-11 23:47   ` Tolunay Orkun
2005-01-12  0:10     ` Wolfgang Denk
2005-01-12  8:09       ` Tolunay Orkun
2005-01-12 13:40         ` Jerry Van Baren [this message]
2005-01-12 16:11           ` Tolunay Orkun
2005-09-24 20:47           ` Wolfgang Denk
2005-09-24 21:26             ` Wolfgang Denk
2005-01-12 14:01         ` Wolfgang Denk
2005-01-12 12:33   ` Jerry Van Baren

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=41E528EA.8040906@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