diff options
author | Gregory Nutt <gnutt@nuttx.org> | 2014-09-11 17:15:26 -0600 |
---|---|---|
committer | Gregory Nutt <gnutt@nuttx.org> | 2014-09-11 17:15:26 -0600 |
commit | e896f974831f25d7994cf12a2170c68a63879c4c (patch) | |
tree | e4b613327656cd0e05bebd5cd446cbf213540936 | |
parent | c0e2f523bda5849e2a176a745aba23e99940f1a6 (diff) | |
download | nuttx-e896f974831f25d7994cf12a2170c68a63879c4c.tar.gz nuttx-e896f974831f25d7994cf12a2170c68a63879c4c.tar.bz2 nuttx-e896f974831f25d7994cf12a2170c68a63879c4c.zip |
Update some comments/function headers
-rw-r--r-- | nuttx/arch/arm/src/armv7-a/arm_fullcontextrestore.S | 11 | ||||
-rw-r--r-- | nuttx/binfmt/libpcode/README.txt | 12 |
2 files changed, 16 insertions, 7 deletions
diff --git a/nuttx/arch/arm/src/armv7-a/arm_fullcontextrestore.S b/nuttx/arch/arm/src/armv7-a/arm_fullcontextrestore.S index 1f10b8dde..b1885a778 100644 --- a/nuttx/arch/arm/src/armv7-a/arm_fullcontextrestore.S +++ b/nuttx/arch/arm/src/armv7-a/arm_fullcontextrestore.S @@ -70,6 +70,15 @@ /**************************************************************************** * Name: up_fullcontextrestore + * + * Description: + * Restore the specified task context. Full prototype is: + * + * void up_fullcontextrestore(uint32_t *restoreregs) noreturn_function; + * + * Return: + * None + * ****************************************************************************/ .globl up_fullcontextrestore @@ -83,7 +92,7 @@ up_fullcontextrestore: #ifdef CONFIG_ARCH_FPU /* First, restore the floating point registers. Lets do this before we - * restore the arm registers so that we have plentry of registers to + * restore the ARM registers so that we have plenty of registers to * work with. */ diff --git a/nuttx/binfmt/libpcode/README.txt b/nuttx/binfmt/libpcode/README.txt index 05e5575e8..a8f482215 100644 --- a/nuttx/binfmt/libpcode/README.txt +++ b/nuttx/binfmt/libpcode/README.txt @@ -128,12 +128,12 @@ Issues and the apps/ directory. That should not be the case; the nuttx/ logic should be completely independent of apps/ logic (but not vice versa). -2. The current implementation will not work in the CONFIG_KERNEL_BUILD. - This is because of the little proxy logic (function pcode_proxy() in the - file pcode.c). (a) That logic would attempt to link with P-code logic - that resides in user space. That will not work. And (2) that proxy - would be started in user mode but in the kernel address space which will - certainly crash immediately. +2. The current implementation will not work in the CONFIG_BUILD_PROTECTED or + CONFIG_BUILD_KERNEL configurations. That is because of the little proxy + logic (function pcode_proxy() in the file pcode.c). (a) That logic would + attempt to link with P-code logic that resides in user space. That will + not work. And (2) that proxy would be started in user mode but in the + kernel address space which will certainly crash immediately. The general idea to fix both of these problems is as follows: |