diff options
| author | Gregory Nutt <gnutt@nuttx.org> | 2014-09-16 13:58:55 -0600 |
|---|---|---|
| committer | Gregory Nutt <gnutt@nuttx.org> | 2014-09-16 13:58:55 -0600 |
| commit | 877af73187ac7fc4a75f5f80542274b77b10ae83 (patch) | |
| tree | b2c46a04933bc7bfb6fe8fe36cc96a3498e3d19e /nuttx/TODO | |
| parent | 4355a56598bb457c14c5eddf7e23293fc6c2329e (diff) | |
| download | nuttx-877af73187ac7fc4a75f5f80542274b77b10ae83.tar.gz nuttx-877af73187ac7fc4a75f5f80542274b77b10ae83.tar.bz2 nuttx-877af73187ac7fc4a75f5f80542274b77b10ae83.zip | |
Update TODO and a README
Diffstat (limited to 'nuttx/TODO')
| -rw-r--r-- | nuttx/TODO | 32 |
1 files changed, 2 insertions, 30 deletions
diff --git a/nuttx/TODO b/nuttx/TODO index b202e9690..219ba8344 100644 --- a/nuttx/TODO +++ b/nuttx/TODO @@ -1,4 +1,4 @@ -NuttX TODO List (Last updated September 13, 2014) +NuttX TODO List (Last updated September 16, 2014) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This file summarizes known NuttX bugs, limitations, inconsistencies with @@ -12,7 +12,7 @@ nuttx/ (2) Memory Managment (mm/) (3) Signals (sched/, arch/) (2) pthreads (sched/) - (9) Kernel/Protected Builds + (8) Kernel/Protected Builds (4) C++ Support (6) Binary loaders (binfmt/) (13) Network (net/, drivers/net) @@ -471,34 +471,6 @@ o Kernel/Protected Build improvement. However, there is no strong motivation now do do that partitioning work. - Title: ARMVv7-A STACK ISSUE - Description: Currently a program running as a process in the kernel build mode - cannot run other programs that reside on the file system. Why? - Because in order to run those other programs, the new program's - address environment must be instantiated in memory to load the - .text and .data and to allocate the initial user space components - from the new user heap. - - However, the previous program's stack currently resides in its - heap. So when a process tries to run another program, its heap - is unmapped and the system crashes. - - The fix is to add a separate stack in a separate memory region - that does not get unmapped when creating new processes. There - are hooks in place to do this; I just need to get time to get - that done. - - UPDATE: I don't think it is that simple. Startup logic will need - to access the new stack in its correct location to do things like - setup task arguments. So I don't think that there is anyway to - do that without losing the current stack. - - I may have to do the Linux solution: Two stacks for each thread: - The main user stack, and a tiny kernel mode stack. - Status: Open - Priority: Pretty high... the kernel build is useless without this - capability. - o C++ Support ^^^^^^^^^^^ |