Update TODO list and NSH documentation

This commit is contained in:
Gregory Nutt
2016-07-20 10:45:21 -06:00
parent e07bd757ba
commit aa8a52aacd
2 changed files with 13 additions and 3 deletions
+2 -2
View File
@@ -8,7 +8,7 @@
<tr align="center" bgcolor="#e4e4e4"> <tr align="center" bgcolor="#e4e4e4">
<td> <td>
<h1><big><font color="#3c34ec"><i>NuttShell (NSH)</i></font></big></h1> <h1><big><font color="#3c34ec"><i>NuttShell (NSH)</i></font></big></h1>
<p>Last Updated: February 8, 2016</p> <p>Last Updated: July 20, 2016</p>
</td> </td>
</tr> </tr>
</table> </table>
@@ -3277,7 +3277,7 @@ nsh&gt;
</tr> </tr>
<tr> <tr>
<td><b><code>mkfifo</code></b></td> <td><b><code>mkfifo</code></b></td>
<td><code>CONFIG_NFILE_DESCRIPTORS</code> &gt; 0</td> <td><code>CONFIG_NFILE_DESCRIPTORS</code> &gt; 0 &amp;&amp; <code>CONFIG_PIPES</code></td>
<td><code>CONFIG_NSH_DISABLE_MKFIFO</code></td> <td><code>CONFIG_NSH_DISABLE_MKFIFO</code></td>
</tr> </tr>
<tr> <tr>
+11 -1
View File
@@ -1,4 +1,4 @@
NuttX TODO List (Last updated July 3, 2016) NuttX TODO List (Last updated July 20, 2016)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This file summarizes known NuttX bugs, limitations, inconsistencies with This file summarizes known NuttX bugs, limitations, inconsistencies with
@@ -447,6 +447,7 @@ o Kernel/Protected Build
mkfatfs mkfatfs mkfatfs mkfatfs
mkrd ramdisk_register() mkrd ramdisk_register()
ping icmp_ping() ping icmp_ping()
mount foreach_mountpoint()
The busybox mkfatfs does not involve any OS calls; it does The busybox mkfatfs does not involve any OS calls; it does
its job by simply opening the block driver (using open/xopen) its job by simply opening the block driver (using open/xopen)
@@ -1399,6 +1400,15 @@ o File system / Generic drivers (fs/, drivers/)
socket structures. There really should be one array that socket structures. There really should be one array that
is a union of file and socket descriptors. Then socket and is a union of file and socket descriptors. Then socket and
file descriptors could lie in the same range. file descriptors could lie in the same range.
Another example of how the current implementation limits
functionality: I recently started an implement of the FILEMAX
(using pctl() instead sysctl()). My objective was to be able
to control the number of available file descriptors on a task-
by-task basis. The complexity due to the partitioning of
desciptor space in a range for file descriptors and a range
for socket descriptors made this feature nearly impossible to
implement.
Status: Open Status: Open
Priority: Low Priority: Low