diff --git a/TODO b/TODO
index b63ea6f6464..8812ad5fade 100644
--- a/TODO
+++ b/TODO
@@ -1,4 +1,4 @@
-NuttX TODO List (Last updated August 6, 2015)
+NuttX TODO List (Last updated August 11, 2015)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 This file summarizes known NuttX bugs, limitations, inconsistencies with
@@ -16,7 +16,7 @@ nuttx/
   (0)  Message Queues (sched/mqueue)
   (4)  C++ Support
   (6)  Binary loaders (binfmt/)
- (12)  Network (net/, drivers/net)
+ (13)  Network (net/, drivers/net)
   (4)  USB (drivers/usbdev, drivers/usbhost)
  (12)  Libraries (libc/, libm/)
  (11)  File system/Generic drivers (fs/, drivers/)
@@ -990,6 +990,22 @@ o Network (net/, drivers/net)
   Priority:    Low.  I don't know of any issues now, but I am sure that
                someone will encounter this in the future.
 
+  Title:       USING send() WITH UDP CONNECTIONS.
+  Description: Currently send is not implemented unless TCP is enabled.  If
+               TCP is enabled and send() is called with a UDP socket, send()
+               will fail with EDESTADDRREQ.  According to OpenGroup.org:
+
+                 "The send() function shall initiate transmission of a message
+                  from the specified socket to its peer. The send() function
+                  shall send a message only when the socket is connected
+                  (including when the peer of a connectionless socket has been
+                  set via connect()).
+
+               This means that, internally, send() should detect the "connected"
+               UDP socket and automatically call sendto().
+  Status:      Open
+  Priority:    Low, there is always the work-around of just calling sendto().
+
 o USB (drivers/usbdev, drivers/usbhost)
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
diff --git a/arch b/arch
index 56596fd0001..5d220dfb291 160000
--- a/arch
+++ b/arch
@@ -1 +1 @@
-Subproject commit 56596fd0001c1906600d7806e67e92040ed99183
+Subproject commit 5d220dfb291e8184b71fd13590e820a6026b7770