Added Rhealstone benchmark to testsuites

The Rhealstone benchmarks six operations that are critical components
of a real-time system. It allows for an objective analysis to be
performed, and allows for comparisons between systems.
See rhealstone/README for more information.
rhealstone/README: Formatting
rhealstone/*.c: Add Print_Warning() call to indicate debug enabled
rhealstone: Add rh prefix to all test names

This makes them easier to spot as a group in wildcard searches.
libcsupport: implemented termios functions cfsetspeed and cfmakeraw
fsbdpart01.doc: Add contents
fsdosfsformat01.doc: Add contents
spfifo02: Clean up output
psximfs02: Clean up output
rhealstone: Add start end and messages
fstests and libtests: Add contents to multiple documentation files
av5282: Improve Doxygen

Add doxygen to the header files in the av5282/include directory.
genmcf548x: Improve Doxygen

Add doxygen to the header files in the genmcf548x/include directory.
shared vmeUniverse: Improve Doxygen
sp16, sp17, and sp20: Documentation Fixes

Fix the documentation for the sp16, sp17 and sp20 tests.
m68k/gen68360: Improve Doxygen
powerpc/mvme3100: Improve Doxygen
libcsupport: Refactor rtems_deviceio_errno

Renames rtems_deviceio_errno to rtems_status_code_to_errno and
integrates it into the Classic API Status Handler. This function
can now be called by including status.h
PR 1548: ERC32 console stops working when UART error flags are set

Problem:

The console works fine when only transmitting data from the ERC32, but stops
working after a while when receiving data.

"Stops working" means, bytes are neither sent nor received from the UART, but
the rest of the system keeps functioning (task are executing, the operative
system is responsive, etc).

Context:

- When an RX error occurs, the ERC32 UARTS stop generating RX/TX interrupts
until the corresponding error flag in the UART_STATUS are cleared.

- The console.c code currently cleans the error flags from the console_isr_x
subroutines, but those are NOT called when an RX error occurs. Thus the error
flag is never cleaned and then the UARTs stop generating interrupts
indefinitely.

- The ERC32 UARTs generate a different interrupt when an RX error occurs.

Fixed by:

- Adding a third interrupt service routine console_isr_error to handle the
UART_ERROR trap. This isr cleans the error flags of the channels.

- Cleaning the error flags manually just after having initialized the interrupt
vectors. This is because if the error flag was already set by the time the
interrupt vectors are configured, the interrupts might never be called.
NTP: Sync time correctly when receiving broadcast updates

1) The value of rtems_bsdnet_ntpserver_count is equal to 0 when no
   server is set, so the check for (rtems_bsdnet_ntpserver_count < 0)
   in rtems_bsdnet_get_ntp() is wrong.  The check should be "<= 0".

2) Binding the listening socket port to 0 does not work.  Packets
   appear on the interface, but the recvfrom in tryServer() never
   returns.  Changing this to the well known NTP socket 123 allows
   the packets to be seen.

3) In tryServer(), an explicit check for NTP version 3 packets is made.
   If the NTP server is version 4, this check fails even though the
   packets seem to be the right shape.