sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated to documentation and README files

Browse Source
This commit is contained in:
Gregory Nutt 2013-04-11 06:53:26 -06:00
parent c05875e93a
commit 1ca14e3555
3 changed files with 33 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
Documentation/NuttX.html
View File

@ -8,7 +8,7 @@
<tr align="center" bgcolor="#e4e4e4">
<td>
<h1><big><font color="#3c34ec"><i>NuttX RTOS</i></font></big></h1>
<p>Last Updated: April 1, 2013</p>
<p>Last Updated: April 10, 2013</p>
</td>
</tr>
</table>
@ -2417,11 +2417,11 @@ nsh>
</p>
<ul>
<b>STATUS:</b>
This is still a work in progess.
At present there is a working basic port with OS verification, Nuttshell (<a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH</a>) configurations, and a graphics test configuration.
The NSH configuration includes verfied support for (DMA-based) SD card interface.
SDRAM is working.
The LCD driver is not functional as of this writing, but is actively underwork and is expected to be available in the NuttX-6.27 release.
The frame-buffer LCD driver is functional and the touchscreen interface is actively underwork.
Both should be available in the NuttX-6.27 release.
</ul>
</td>
</tr>
@ -2650,13 +2650,13 @@ nsh>
<p>
<b>TI Stellaris LM4F120</b>.
This port uses the TI Stellaris LM4F120 LaunchPad.
Jose Pablo Carballo is doing this port.
Jose Pablo Carballo and I are doing this port.
</p>
<ul>
<p>
<b>STATUS:</b>
As of this writing, the basic port is code complete but still untested.
The fully verified LM4F120 LaunchPad port is expected in NuttX-6.27.
As of this writing, the basic port is code complete and fully verified configurations exit for the basic NuttX OS test and for the NuttShell <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH</a>).
The first fully functional LM4F120 LaunchPad port was released in NuttX-6.27.
</p>
</ul>
</td>

17
TODO
View File

@ -1,4 +1,4 @@
NuttX TODO List (Last updated March 24, 2013)
NuttX TODO List (Last updated April 10, 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/)
(7) Kernel Build
(8) Kernel Build
(2) C++ Support
(6) Binary loaders (binfmt/)
(16) Network (net/, drivers/net)
@ -450,6 +450,19 @@ o Kernel Build
Status: Open
Priority: Low (unless security becomes an issue).
Title: MICRO-KERNEL
Description: The initial kernel build cut many interfaces at a very high level.
The resulting monolithic kernel is then rather large. it would
not be a prohibitively large task to reorganize the interfaces so
that NuttX is built as a micro-kernel, i.e., with only the core
OS services within the kernel and with other OS facilities, such
as the file system, to reside in user-space and to interface with
those core OS facilities through traps.
Status: Open
Priority: Low. This is a good idea and certainly an architectural
improvement. However, there is no strong motivivation now do
do that partitioning work.
o C++ Support
^^^^^^^^^^^

14
configs/qemu-i486/README.txt
View File

@ -90,8 +90,18 @@ Toolchains
not produce ELF final binaries but, rather, DOS MZ executables (i.e., .exe
files). Those cannot be used with QEMU.
The file */setenv.sh should be modified to point to the correct path to the
GCC toolchain (if different from the default in your PATH variable).
NOTE: It has also been reported to me that with a certain Ubuntu virtual
installation, the native x86 did not build correct i486 code. Other
installations of the same vintage do not have such issues. However,
there is always a possibility that any GCC release will be incompatible
with i486. That fallback used by this person in this particular case
was to use the Buildroot i486 cross-development tool described below. I
suspect that this was not necessary, but it was a simple work-around
that allowed that person to build a work-able system.
In any event, the file */setenv.sh should be modified to point to the correct
path to the GCC toolchain (if different from the default in your PATH
variable).
Cygwin Buildroot Toolchain
--------------------------