* lib/rtems_bsdnet_ntp.c: Modifications to make the RTEMS NTP
synchronization a little more robust -- no NTP daemon yet, but
at least it trys a little harder when the primary NTP server is down.
* lib/tftpDriver.c: Reduce first timeout interval. This
improves throughput on systems which are dropping packets.
Only the first timeout is reduced. This keeps the number
of extra packets down on networks that are very busy and
dropping lots of packets.
* lib/tftpDriver.c: add comments to handlers struct function pointers.
* rtems/rtems_glue.c: move pointer arithmetic to be _after_
pointer has been checked against NULL.
that contains the automake files for libnetworking plus a couple of
minor fixes. [Now only one unused/unsupported Makefile.in remains
(./c/src/lib/libbsp/hppa1.1/pxfl/Makefile.in).]
To apply:
patch -p1 < rtems-rc-20000118-7.diff
/bin/sh rtems-rc-20000118-7.rm
/bin/sh rtems-rc-20000118-7.add
./bootstrap
Notes:
* I have tested this one by building all BSPs for m68k, powerpc, sh and
unix with toolchains built since last weekend.
* I did not touch libnetworking's directory layout.
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.
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.
Joel Sherrill