summaryrefslogtreecommitdiff
path: root/nuttx/binfmt/libpcode
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2014-05-10 11:36:20 -0600
committerGregory Nutt <gnutt@nuttx.org>2014-05-10 11:36:20 -0600
commitc5614e5b45fd99eb92ae7807f2132c956ff70147 (patch)
tree85ee2880657de81a9cd866f1cac9ba6ede3ce9ec /nuttx/binfmt/libpcode
parent3e75c2da3aa372c71e2543f00c50d8d3abb6002e (diff)
downloadnuttx-c5614e5b45fd99eb92ae7807f2132c956ff70147.tar.gz
nuttx-c5614e5b45fd99eb92ae7807f2132c956ff70147.tar.bz2
nuttx-c5614e5b45fd99eb92ae7807f2132c956ff70147.zip
Updated README and comments
Diffstat (limited to 'nuttx/binfmt/libpcode')
-rw-r--r--nuttx/binfmt/libpcode/README.txt11
1 files changed, 10 insertions, 1 deletions
diff --git a/nuttx/binfmt/libpcode/README.txt b/nuttx/binfmt/libpcode/README.txt
index d8fcc7f32..05e5575e8 100644
--- a/nuttx/binfmt/libpcode/README.txt
+++ b/nuttx/binfmt/libpcode/README.txt
@@ -150,7 +150,16 @@ The general idea to fix both of these problems is as follows:
on the command line. This might be accomplished by simply modifying the
argv[] structure in the struct binary_s instance.
+ The current start-up logic in binfmt_execmodule.c would have modified to
+ handle this special start-up. Perhaps the struct binfmt_s could be
+ extended to include an exec() method that provides custom start up logic?
+
4. Add a task start hook to the program. Here is where we can setup up the
on_exit() function that will clean up after the P-Code program terminates.
-There are many other smaller issues to be resolved, but those are the main ones.
+There are many other smaller issues to be resolved, but those are the main
+ones.
+
+A more complex solution might include a user-space p-code daemon that
+receives the P-Code path in a POSIX message and starts a P-Code interpreter
+thread wholly in user space.