From e2d9a69df23894921f553f0a44b64a4b1ea7f999 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Mon, 18 Aug 2014 07:24:47 -0600 Subject: Update README files, Kconfig help comments, and make the network monitor not EXPERIMENTAL --- apps/nshlib/Kconfig | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'apps/nshlib') diff --git a/apps/nshlib/Kconfig b/apps/nshlib/Kconfig index 7bf8f32fa..b51b2931e 100644 --- a/apps/nshlib/Kconfig +++ b/apps/nshlib/Kconfig @@ -813,7 +813,7 @@ if NSH_NETINIT_THREAD config NSH_NETINIT_MONITOR bool "Monitor link state" default n - depends on ARCH_PHY_INTERRUPT && NETDEV_PHY_IOCTL && NET_UDP && !DISABLE_SIGNALS && EXPERIMENTAL + depends on ARCH_PHY_INTERRUPT && NETDEV_PHY_IOCTL && NET_UDP && !DISABLE_SIGNALS ---help--- By default the net initialization thread will bring-up the network then exit, freeing all of the resources that it required. This is a @@ -822,10 +822,12 @@ config NSH_NETINIT_MONITOR If this option is selected, however, then the network initialization thread will persist forever; it will monitor the network status. In the event that the network goes down (for example, if a cable is - removed), then the the thread will monitor the link status and + removed), then the thread will monitor the link status and attempt to bring the network back up. In this case the resources required for network initialization are never released. +if NSH_NETINIT_MONITOR + config NSH_NETINIT_SIGNO int "Notification signal number" default 18 @@ -834,8 +836,6 @@ config NSH_NETINIT_SIGNO change in the link status. This setting may be used to customize that signal number in order to avoid conflicts. -if NSH_NETINIT_MONITOR - config NSH_NETINIT_RETRYMSEC int "Network bring-up retry period (msec)" default 2000 -- cgit v1.2.3