summaryrefslogtreecommitdiff
path: root/nuttx/binfmt
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2014-09-11 17:15:26 -0600
committerGregory Nutt <gnutt@nuttx.org>2014-09-11 17:15:26 -0600
commite896f974831f25d7994cf12a2170c68a63879c4c (patch)
treee4b613327656cd0e05bebd5cd446cbf213540936 /nuttx/binfmt
parentc0e2f523bda5849e2a176a745aba23e99940f1a6 (diff)
downloadpx4-nuttx-e896f974831f25d7994cf12a2170c68a63879c4c.tar.gz
px4-nuttx-e896f974831f25d7994cf12a2170c68a63879c4c.tar.bz2
px4-nuttx-e896f974831f25d7994cf12a2170c68a63879c4c.zip
Update some comments/function headers
Diffstat (limited to 'nuttx/binfmt')
-rw-r--r--nuttx/binfmt/libpcode/README.txt12
1 files changed, 6 insertions, 6 deletions
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: