TCP networking:  In the TCP connection operation, it was trying to setup the network monitor BEFORE the socket was successfully connected.  This, of course, has ALWAYS failed because the socket is not yet connected and the TCP state is not yet correct for a connected socket.  However, because of other changes net_startmonitor(0 no returns a failure condition that causes worse problems when trying to connect.  The fix is to move the logic that starts the network monitor to AFTER the socket has been successfully connected.

Networking:  The network device list was protected by a re-entrant semaphore.  With the recent change to support network device callback, the network stack needs to access the network device list too. Some drivers, however, run the network stack from the interrupt level -- this is bad but a fact in the current state.  Of course,those drivers are unable to take the semaphore and will assert.

The solution here is to eliminate the device devices semaphore altogether.  This eliminates netdev_semtake() and netdev_semgive() and replaces them with net_lock() and net_unlock() which have larger scope as needed for this purpose.

TCP networking: Since the network monitor now allocates a callback structure, it is critical to make sure that the networking monitor is stopped when the socket is closed or any other loss of connection.  What was innocuous before would now be a memory leak

Add an option to disable support for long long formats in lib_vsprintf.  From Alan Carvalho de Assis

Networking: Get rid of g_ipv4_allzeroaddr and g_ipv4_alloneaddr.  It is more efficient and more intuitive to use INADDR_ANY and INADDR_BROADCAST

Conflicts:
	nuttx/ChangeLog

STM32 F4 Discovery: Move up_cxxinitialize from nuttx/configs/stm32f4discovery/src to apps/platform/stm32f4discovery where it belongs.

Conflicts:
	nuttx/ChangeLog

Networking: setsockopt() fails when setting timeouts to values less that an 100 msec.  That is because the timeout is limited to stops of 1 decisecond and because the conversion of structure timeval was truncating the microsecond remainder.  The utility net_timeval2dsec now accespts and option to determin how it handles the remainder:  truncate, discarding the remainder, use the remainder to round to the closed decisecond value, or use any non-zero remainder to the next larger whole decisecond value.

For the setsockopt() case, it will always use the final option.  This means that a time of zero (i.e., not timeout) can only occur if the value zero was explicated provided to setsockopt().

Conflicts:
	nuttx/net/devif/devif_callback.c

Conflicts:
	nuttx/ChangeLog

Networking: Modify event list handling:  Now there are two event lists each device structure:  (1) One is for ARP and ICMP data related evetns, the other is for device related events.  Callback allocation/free routines no accept a device paramter as well as a list: If the device paramter is added, then the callback goes into both the connection-related liast AND the device event list.  Thus each socket type can received both custom data-related events as well as common device related events.