| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
more flexible about the error status returned from a timeout.
|
|
|
|
|
|
|
|
|
| |
report by Nick.SIMON@syntegra.bt.co.uk:
TFTP uses UDP and UDP packets are prime targets for getting dropped when
the network gets busy. I want the number of retries quite large in my
application. I see that PACKET_REPLY_MILLISECONDS is, in fact, not
being used.
|
| |
|
|
|
|
|
|
| |
system table from when the rtems_filesystem_operations_table structure changed
and the initializer in libnetworking/lib/tftpDriver.c did not get
updated.
|
|
|
|
|
| |
Patches against 1105 snapshot to add NTP server support to network
configuration/BOOTP.
|
|
|
|
| |
the minor number indicated the port number to try.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I get the following warning when compiling the latest snapshot. I had
a quick look at the source -- it certainly looks to me like this is a
real bug.
../../../../src/rtems-19990709/c/src/lib/libc/mount.c:97: warning:
`options' might be used uninitialized in this function
Also, I changed the TFTP test program and TFTP driver to reflect the
changes in the way paths are passed to the TFTP driver. The TFTP driver
now needs a proper `dotted-decimal' hostname as the second component of
the path name.
|
|
|
|
| |
mount() was changed to avoid the use of a string as the options.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|