From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bartlomiej Sieka <tur@semihalf.com>
Date: Thu, 25 Sep 2008 08:17:07 +0200
Subject: [U-Boot] [PATCH 1/3] net: Make TFTP server timeout configurable
In-Reply-To: <20080922204213.87B33248EE@gemini.denx.de>
References: <12217502093845-git-send-email-tur@semihalf.com>
	<12217502101894-git-send-email-tur@semihalf.com>
	<48D27108.4060406@ge.com> <48D33E23.3020502@semihalf.com>
	<20080922204213.87B33248EE@gemini.denx.de>
Message-ID: <48DB2CE3.5050202@semihalf.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang Denk wrote:
> Dear Bartek,
> 
> In message <48D33E23.3020502@semihalf.com> you wrote:
>>> Are seconds an appropriate scale factor for the timeout?
> ...
>> The patch didn't introduce changes in this regard -- TFTP timeouts were
>> defined in seconds originally. The patch makes the timeout behavior
>> configurable, instead of being hardcoded, but the units remain the same:
> 
> But the argument was a perfectly valid one. I am, too, concerned that
> second resolution is not optimal any more (it was as long as we needed
> just one timeout long enough, but this situation will be changed by
> your other patches).
> 
> So please extend that patch to change this into milliseconds as
> discussed before.

OK, v2 of the patches will implement milisecond granularity for initial
TFTP server timeout.

Regards,
Bartlomiej Sieka