diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html index 7ea3e39c138..3bfd4021fd5 100644 --- a/Documentation/NuttxPortingGuide.html +++ b/Documentation/NuttxPortingGuide.html @@ -3098,6 +3098,7 @@ VxWorks provides the following comparable interface:
Function Prototype:
+#include <nuttx/wqueue.h>
int work_queue(int qid, FAR struct work_s *work, worker_t worker,
FAR void *arg, uint32_t delay);
@@ -3156,6 +3157,7 @@ int work_queue(int qid, FAR struct work_s *work, worker_t worker,
work_cancel()Function Prototype: +#include <nuttx/wqueue.h> int work_cancel(int qid, FAR struct work_s *work);
@@ -3197,6 +3199,7 @@ int work_cancel(int qid, FAR struct work_s *work);
work_signal()Function Prototype: +#include <nuttx/wqueue.h> int work_signal(int qid);
@@ -3228,6 +3231,7 @@ int work_signal(int qid);
Function Prototype:
+#include <nuttx/wqueue.h> bool work_available(FAR struct work_s *work);@@ -3258,6 +3262,8 @@ bool work_available(FAR struct work_s *work);
Function Prototype:
+#include <nuttx/config.h> +#include <nuttx/wqueue.h> #if defined(CONFIG_LIB_USRWORK) && !defined(__KERNEL__) int work_usrstart(void); #endif @@ -3283,6 +3289,8 @@ int work_usrstart(void);Function Prototype:
+#include <nuttx/config.h> +#include <nuttx/wqueue.h> #if defined(CONFIG_SCHED_LPWORK) && defined(CONFIG_PRIORITY_INHERITANCE) void lpwork_boostpriority(uint8_t reqprio); #endif @@ -3311,6 +3319,8 @@ void lpwork_boostpriority(uint8_t reqprio);Function Prototype:
+#include <nuttx/config.h>
+#include <nuttx/wqueue.h>
#if defined(CONFIG_SCHED_LPWORK) && defined(CONFIG_PRIORITY_INHERITANCE)
void lpwork_restorepriority(uint8_t reqprio);
#endif
@@ -3395,7 +3405,7 @@ void lpwork_restorepriority(uint8_t reqprio);
Tasking Support.
Other interfaces must be provided to support higher-level interfaces used by the NuttX tasking logic.
- These interfaces are* used by the functions in sched/ and all operate on the task group which as been assigned an address environment by up_addrenv_clone().
+ These interfaces are used by the functions in sched/ and all operate on the task group which as been assigned an address environment by up_addrenv_clone().
Dynamic Stack Support.
CONFIG_ARCH_STACK_DYNAMIC=y indicates that the user process stack resides in its own address space.
- This options is also required if CONFIG_BUILD_KERNEL and CONFIG_LIBC_EXECFUNCS are selected.
+ This option is also required if CONFIG_BUILD_KERNEL and CONFIG_LIBC_EXECFUNCS are selected.
Why?
Because the caller's stack must be preserved in its own address space when we instantiate the environment of the new process in order to initialize it.