Update README files, Kconfig help comments, and make the network monitor not EXPERIMENTAL

1 files changed, 2 insertions, 57 deletions

diff --git a/nuttx/TODO b/nuttx/TODO
index 50117d83f..df6014ca3 100644
--- a/nuttx/TODO
+++ b/nuttx/TODO
@@ -1,4 +1,4 @@
-NuttX TODO List (Last updated August 11, 2014)
+NuttX TODO List (Last updated August 18, 2014)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 This file summarizes known NuttX bugs, limitations, inconsistencies with
@@ -49,7 +49,7 @@ nuttx/
 apps/
 
   (4)  Network Utilities (apps/netutils/)
-  (5)  NuttShell (NSH) (apps/nshlib)
+  (3)  NuttShell (NSH) (apps/nshlib)
   (1)  System libraries apps/system (apps/system)
   (5)  Other Applications & Tests (apps/examples/)
 
@@ -2313,61 +2313,6 @@ o NuttShell (NSH) (apps/nshlib)
   Status:      Open
   Priority:    Low (enhancement)
 
-  Title:       NETWORK BRINGUP
-  Description: If the network is available on reset, then there is really
-               no problem.  Negotiating the link will take only a second or
-               so and the delay to the NSH prompt is normally acceptable.
-
-               But if there is no network connected, then the start-up delay
-               can be very long depending upon things like the PHY, timeout
-               delay times, and numbers of retries.  A failed negotiation
-               can take a very long time, perhaps as much as a minute...
-               Long enough that you would think that the board would never
-               come up.
-
-               The problem is that all of the initialization is sequential:
-               NSH does not run until each sequential initialization step is
-               completed.
-
-               There is an option enabled by CONFIG_NSH_NETINIT_THREAD that
-               will do the network bring-up asynchronously in parallel on
-               a separate thread.  This eliminates the networking delay
-               altogether.  The initial implementation, however, has some
-               limitations:
-
-               - If no network is connected, the network bring-up will fail
-                 and the network initialization thread will simply exit.
-                 There are no retries and no mechanism to know if the network
-                 initialization was successful.
-
-               - Furthermore, there is currently no support for detecting loss
-                 of network connection and recovery of the connection (see the
-                 next issue).
-  Status:      Open
-  Priority:    Medium, but certainly high if you plan to use the generic
-               NSH in a product with a network.
-
-  Title:       LOSS OF CONNECTION
-  Description: There is no logic in place no to detect that the network
-               connection has been lost (if the cable has been unplugged,
-               for example).  And also no logic to bring the network back
-               up when the link can be re-established.
-
-               This is normally done by catching a GPIO interrupt from a
-               PHY.  This is logic outside of the Ethernet MAC driver
-               (although the Ethernet MAC driver would also have to
-               support the PHY operations to determine the link state).
-               Some of the boards provide logic to connect to the PHY
-               interrupt.  Like:
-
-                 xcpt_t arc_phy_irq(FAR const char *intf, xcpt_t irqhandler);
-
-               (prototyped in include/nuttx/arch.h). But that interrupt is
-               not used by anything now.
-  Status:      Open
-  Priority:    Medium.
-
-  Status:      Open
 o System libraries apps/system (apps/system)
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^