Add kernel build support for Stellaris, Kinetis, LPC43, and NUC1xx MCUs

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5781 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo
2013-03-24 17:28:38 +00:00
parent 0b6910fe7c
commit fde971ed5d
36 changed files with 2251 additions and 88 deletions
+17 -2
View File
@@ -1,4 +1,4 @@
NuttX TODO List (Last updated March 8, 2013)
NuttX TODO List (Last updated March 24, 2013)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This file summarizes known NuttX bugs, limitations, inconsistencies with
@@ -10,7 +10,7 @@ nuttx/
(1) Memory Managment (mm/)
(3) Signals (sched/, arch/)
(2) pthreads (sched/)
(6) Kernel Build
(7) Kernel Build
(2) C++ Support
(6) Binary loaders (binfmt/)
(16) Network (net/, drivers/net)
@@ -376,6 +376,9 @@ o Kernel Build
depend on kernel internal, non-standard interfaces that are not
accessible in user-space. These are both critical NSH commands
and need to be supported.
In addition, the NSH 'free' command only shows memory usage in
the user headp, not useage in the kernel heap.
Status: Open
Priority: High. I really like these commands!
@@ -437,6 +440,18 @@ o Kernel Build
Status: Open
Priority: Low (unless performance becomes an issue).
Title: MEMORY MANAGER SECURITY ISSUE
Description: In the current designed, the kernel code calls into the user-space
allocators to allocate user-space memory. It is a security risk to
call into user-space in kernel-mode because that could be exploited
to gain control of the system. That could be fixed by dropping to
user mode before trapping into the memory allocators; the memory
allocators would then need to trap in order to return (this is
already done to return from signal handlers; that logic could be
renamed more generally and just used for a generic return trap).
Status: Open
Priority: Low (unless security becomes an issue).
o C++ Support
^^^^^^^^^^^