OrgApache/incubator-nuttx
OrgApache
/
incubator-nuttx
mirror of https://github.com/apache/incubator-nuttx.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Upate TODO list to reflect consequences of commit 3b1cc69d68

This commit is contained in:
Gregory Nutt 2018-09-26 10:27:50 -06:00
parent 910e7a3899
commit 6e4545a924
1 changed files with 10 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
TODO
View File

@ -1,4 +1,4 @@
NuttX TODO List (Last updated September 19, 2018) NuttX TODO List (Last updated September 26, 2018)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This file summarizes known NuttX bugs, limitations, inconsistencies with This file summarizes known NuttX bugs, limitations, inconsistencies with
@ -228,15 +228,18 @@ o Task/Scheduler (sched/)
and that sets the errno value on failures. and that sets the errno value on failures.
On particularly difficult issue is the use of common memory On particularly difficult issue is the use of common memory
manager C, and NX libraries in the build. For the FLAT manager C, and NX libraries in the build. For the PROTECTED
build, that is not such a issue because the OS internal and KERNEL builds, this issue is resolved. In that case,
versions of the interfaces can be used. But is a difficult The OS links with a different version of the libraries than
problem for PROTECTED and KERNEL builds where the OS links does the application: The OS version would use the OS internal
with a different version of the libraries than does the
application: The OS version would use the OS internal
interfaces and the application would use the standard interfaces and the application would use the standard
interfaces. interfaces.
But for the FLAT build, both the OS and the applications use
the same library functions. For applications, the library
functions *must* support errno's and cancellation and, hence,
these are also used within the OS.
But that raises yet another issue: If the application But that raises yet another issue: If the application
version of the libraries use the standard interfaces version of the libraries use the standard interfaces
internally, then they may generate unexpected cancellation internally, then they may generate unexpected cancellation