sergiotarxz/nuttx-apps
sergiotarxz/nuttx-apps
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Kconfig: Improved comments

Browse Source
This commit is contained in:
OrbitalFox 2015-09-24 08:28:50 -06:00 committed by Gregory Nutt
parent 21a33d9b7a
commit 93876b5af3
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
nshlib/Kconfig
View File

@ -853,15 +853,15 @@ config NSH_NETINIT_THREAD
But if there is no network connected, then the start-up delay can But if there is no network connected, then the start-up delay can
be very long depending upon things like the particular PHY, driver be very long depending upon things like the particular PHY, driver
timeout delay times, and numbers of retries. A failed negotiation timeout delay times and number of retries. A failed negotiation
can potentially take a very long time, perhaps as much as a can potentially take a very long time, perhaps as much as a
minute... Long enough that you might think that the board would minute... Long enough that you might think that the board would
never come up! never come up!
One solution is to enabled by this option. If NSH_NETINIT_THREAD One solution is enabled by this option. If NSH_NETINIT_THREAD
is selected, the network bring-up will all occur in parallel with is selected, the network bring-up will occur in parallel with
NSH on a separate thread. In this case, the NSH prompt will occur NSH on a separate thread. In this case, the NSH prompt will occur
immediately with the network becoming available some time layer (if immediately with the network becoming available some time later (if
if all). This thread will terminate once it successfully initializes if all). This thread will terminate once it successfully initializes
the network the network