Hi Scott, On Tue, Jun 26, 2012 at 1:34 PM, Scott Wood <scottw...@freescale.com> wrote: > On 06/26/2012 10:30 AM, Joe Hershberger wrote: >> Hi Tetsuyuki, >> >> On Tue, Jun 26, 2012 at 3:52 AM, Wolfgang Denk <w...@denx.de> wrote: >>> Dear Tetsuyuki Kobayashi, >>> >>> In message <4fe9711a.2090...@kmckk.co.jp> you wrote: >>>> >>>>>> Are you sure the problems are not in the board specific code? >>>>> OK. I will try the same thing on an in-tree board (maybe, panda board) to >>>>> check if this is board specific or not. >>>> >>>> I did on a panda board. It has the same problem and this patch solves it. >>>> So this is not board specific problem. Please consider to change global >>>> setting of NFS_TIMEOUT in nfs.c. >>> >>> net/nfs.c is not the right place to make board specific adjustments. >>> >>> I am still not convinced this is an issue with the global code. It >>> could be your NFS server as well. >> >> I'm not convinced either. It clearly depends on the speed of your >> server, the speed of the connection, the size of the file you are >> transferring, etc. > > Is the timeout for completing the transfer, or for making forward progress?
The timeout is reset each time that NetSetTimeout() is called. For NFS, that happens when a transfer starts, when the timeout occurs (a retry begins), and when a "read request" response comes from the server. I would bet that means it should be a timeout for making progress, but I'm not an NFS protocol expert. -Joe _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
