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

There used to be two ways to pass parameters to new tasks, depending upon the configuration: Either (1) argv[] as created as an array with each string strdup'ed. Or (1) argv[] array and strings were created on the stack before the new task was started. Now, there is only one way, way (1). Way (2) might be slightly more compact, but this is not worth carry the complexity of two different ways of doing the same thing.

Browse Source
This commit is contained in:
Gregory Nutt 2014-09-01 15:39:34 -06:00
parent 83047cedb6
commit 2cecc4f857
2 changed files with 7 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/NuttX.html
View File

@ -3634,13 +3634,13 @@ Mem: 29232 5920 23312 23312
problems because of SDCC compiler differences.
Refer to the NuttX board <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/misc/Obsoleted/configs/pjrc-8051/README.txt">README</a> file for further information.
</p>
<p>
<b>Obsoleted</b>.
This architecture has been obsoleted.
The code has been moved out of the source tree an can now be found in <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/misc/Obsoleted/">Obsoleted</a> directory.
This support was obsoleted because (1) the architecture limitations of the 8051 family make ongoing support too difficult, and (2) although the basic port was marginally functional, it has never really been demonstrated convincingly in any application.
</p>
</ul>
<p>
<b><i>Obsoleted</i></b>.
This architecture has been <i>obsoleted</i>.
The code has been moved out of the NuttX source tree but can still be found be found in <a href="http://sourceforge.net/p/nuttx/git/ci/master/tree/misc/Obsoleted/">Obsoleted</a> directory.
This support was obsoleted because (1) the architecture limitations of the 8051 family make ongoing development of more advanced NuttX features too difficult, and (2) although the basic port was marginally functional, it has never really been demonstrated convincingly in any application.
</p>
</td>
</tr>
<tr>

5
Documentation/NuttxPortingGuide.html
View File

@ -1870,7 +1870,7 @@ The system can be re-made subsequently by just typing <code>make</code>.
<p>
<b>Description</b>.
Allocate a stack frame in the TCB's stack to hold thread-specific data.
This function may be called anytime after <code>up_create_stack()</code> or <code>up_use_stack()</code> have been called but before the task has been started.
This function may be called any time after <code>up_create_stack()</code> or <code>up_use_stack()</code> have been called but before the task has been started.
</p>
<p>
Thread data may be kept in the stack (instead of in the TCB) if it is accessed by the user code directly.
@ -1889,9 +1889,6 @@ The system can be re-made subsequently by just typing <code>make</code>.
This will still be the initial value of the stack pointer when the task is started.
</li>
</ul>
<p>
This API is <i>NOT</i> required if <code>CONFIG_BUILD_PROTECTED</code> and <code>CONFIG_BUILD_KERNEL</code> are undefined.
</p>
<p><b>Input Parameters:</b></p>
<ul>
<li>