From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Ceresoli Date: Tue, 03 May 2011 14:23:11 +0200 Subject: [U-Boot] [RFC] Act as a TFTP server In-Reply-To: <20110430195342.5FE8FD5270F@gemini.denx.de> References: <4DA5682A.8040203@comelit.it> <20110413113735.3115914F02E@gemini.denx.de> <4DA59B5E.5000105@comelit.it> <20110430195342.5FE8FD5270F@gemini.denx.de> Message-ID: <4DBFF3AF.4040505@comelit.it> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Il 30/04/2011 21:53, Wolfgang Denk ha scritto: > Dear Luca Ceresoli, > > In message<4DA59B5E.5000105@comelit.it> you wrote: >>>> Usage: tftpsrv [] >>>> >>>> This would be used almost like tftpboot, except no file name is specified on >>>> the commandline. >>>> would default to the environment variable. >>> I see some user interface issues here: >>> - When and how do you terminate this command? After a successful >>> download, ok. But how long do we wait for that? Forever? Or do we >>> time out? >> The TFTP client tries sending a RRQ packet TIMEOUT_COUNT times (default 10), >> spaced TIMEOUT msecs (default 5000) from each other. 50 seconds total by default. > Well - this requires that there actually _is_ a TFTP client which > attempts to connect. But there is no guarantee that any such client > is running at all, or that it can connect through firewalls, routers, > etc. > > So assuming we never see any incoming packets - how long will we wait? Once it has started, the server is stopped like the client is: - on a complete file reception - pressing Ctrl-C - after waiting 5 seconds for 10 times. Luca