types blkcnt_t and off_t should not depend on memory model; Remove non-standard type STATUS

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@2330 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2009-12-13 18:01:46 +00:00
parent 4822754c55
commit c2d264378c
3 changed files with 34 additions and 21 deletions

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: December 5 2009</p>
<p>Last Updated: December 13, 2009</p>
</td>
</tr>
</table>
@ -1616,6 +1616,11 @@ nuttx-2010.1 2010-xx-xx Gregory Nutt &lt;spudmonkey@racsa.co.cr&gt;
can be used with any file system. Good performance of this layer will
depend upon functioning write buffer support!
NOTE: FTL support is untested as of the initial check-in.
* Numerous minor changes for m68hc12 to eliminate compilation errors and
warnings due to the fact that it uses 16-bit integer types and for casts
between uint32 (32-bits) and an mc68hc12 pointer (16-bits).
* sys/types: Size of off_t and blkcnt_t should not depend on size of
int in the architecture; Removed non-standard type STATUS
pascal-2010.1 2010-xx-xx Gregory Nutt &lt;spudmonkey@racsa.co.cr&gt;

View File

@ -438,8 +438,10 @@
<li><code>arch/arm/include/lpc214x</code> and <code>arch/arm/src/lpc214x</code>:
These directories provide support for NXP LPC214x family of
processors.
STATUS: This port is in progress and should be available in the
nuttx-0.2.5 release.
STATUS: This port boots and passes the OS test (examples/ostest).
The port is complete and verified. As of NuttX 0.3.17, the port includes:
timer interrupts, serial console, USB driver, and SPI-based MMC/SD card
support. A verified NuttShell configuration is also available.
</li>
</ul>
@ -700,7 +702,14 @@
<li><code>configs/us7032evb1</code>:
This is a port of the Hitachi SH-1 on the Hitachi SH-1/US7032EVB1 board.
STATUS: Work has just began on this port.
STATUS: This port is available as of release 0.3.18 of NuttX. The port is basically
complete and many examples run correctly. However, there are remaining instabilities
that make the port un-usable. The nature of these is not understood; the behavior is
that certain SH-1 instructions stop working as advertised. This could be a silicon
problem, some pipeline issue that is not handled properly by the gcc 3.4.5 toolchain
(which has very limited SH-1 support to begin with), or perhaps with the CMON debugger.
At any rate, I have exhausted all of the energy that I am willing to put into this cool
old processor for the time being.
</li>
<li><code>configs/xtrs</code>:

View File

@ -13,7 +13,7 @@
<h1><big><font color="#3c34ec"><i>NuttX Operating System<p>User's Manual</i></font></big></h1>
<p><small>by</small></p>
<p>Gregory Nutt<p>
<p>Last Updated: May 22, 2009</p>
<p>Last Updated: December 13, 2009</p>
</td>
</tr>
</table>
@ -296,8 +296,8 @@ VxWorks provides the following similar interface:
<b>Function Prototype:</b>
<pre>
#include &lt;sched.h&gt;
STATUS task_init(_TCB *tcb, char *name, int priority, uint32 *stack, uint32 stack_size,
maint_t entry, const char *argv[]);
int task_init(_TCB *tcb, char *name, int priority, uint32 *stack, uint32 stack_size,
maint_t entry, const char *argv[]);
</pre>
<p>
@ -368,7 +368,7 @@ VxWorks provides the following similar interface:
<b>Function Prototype:</b>
<pre>
#include &lt;sched.h&gt;
STATUS task_activate( _TCB *tcb );
int task_activate( _TCB *tcb );
</pre>
<p>
@ -418,7 +418,7 @@ the pointer to the WIND_TCB cast to an integer.
<b>Function Prototype:</b>
<pre>
#include &lt;sched.h&gt;
STATUS task_delete( pid_t pid );
int task_delete( pid_t pid );
</pre>
<p>
@ -514,7 +514,7 @@ And the UNIX interface:
<b>Function Prototype:</b>
<pre>
#include &lt;sched.h&gt;
STATUS task_restart( pid_t pid );
int task_restart( pid_t pid );
</pre>
<p>
@ -974,7 +974,7 @@ priority of the calling task is returned.
<b>Function Prototype:</b>
<pre>
#include &lt;sched.h&gt;
STATUS sched_lock( void );
int sched_lock( void );
</pre>
<p>
@ -994,7 +994,7 @@ number of times) or until it blocks itself.
<p>
<b>Assumptions/Limitations:</b>
<p>
<b> POSIX Compatibility:</b> This is a NON-POSIX interface.
<b>POSIX Compatibility:</b> This is a NON-POSIX interface.
VxWorks provides the comparable interface:
<pre>
STATUS taskLock( void );
@ -1006,7 +1006,7 @@ VxWorks provides the comparable interface:
<b>Function Prototype:</b>
<pre>
#include &lt;sched.h&gt;
STATUS sched_unlock( void );
int sched_unlock( void );
</pre>
<p>
@ -1027,7 +1027,7 @@ eligible to preempt the current task will execute.
<p>
<b>Assumptions/Limitations:</b>
<p>
<b> POSIX Compatibility:</b> This is a NON-POSIX interface.
<b>POSIX Compatibility:</b> This is a NON-POSIX interface.
VxWorks provides the comparable interface:
<pre>
STATUS taskUnlock( void );
@ -2296,7 +2296,7 @@ initialization time).
<b>Function Prototype:</b>
<pre>
#include &lt;wdog.h&gt;
STATUS wd_delete (WDOG_ID wdog);
int wd_delete (WDOG_ID wdog);
</pre>
<p>
@ -2321,7 +2321,7 @@ pointer to a watchdog structure.
caller to assure that the watchdog is inactive before deleting
it.
<p>
<b> POSIX Compatibility:</b> This is a NON-POSIX interface.
<b>POSIX Compatibility:</b> This is a NON-POSIX interface.
VxWorks provides the following comparable interface:
<pre>
STATUS wdDelete (WDOG_ID wdog);
@ -2340,7 +2340,7 @@ before deallocating it (i.e., never returns ERROR).
<b>Function Prototype:</b>
<pre>
#include &lt;wdog.h&gt;
STATUS wd_start( WDOG_ID wdog, int delay, wdentry_t wdentry,
int wd_start( WDOG_ID wdog, int delay, wdentry_t wdentry,
intt argc, ....);
</pre>
@ -2378,7 +2378,7 @@ wd_start() on a given watchdog ID has any effect.
context of the timer interrupt handler and is subject to all ISR
restrictions.
<p>
<b> POSIX Compatibility:</b> This is a NON-POSIX interface.
<b>POSIX Compatibility:</b> This is a NON-POSIX interface.
VxWorks provides the following comparable interface:
<pre>
STATUS wdStart (WDOG_ID wdog, int delay, FUNCPTR wdentry, int parameter);
@ -2397,7 +2397,7 @@ number of parameters is determined by
<b>Function Prototype:</b>
<pre>
#include &lt;wdog.h&gt;
STATUS wd_cancel (WDOG_ID wdog);
int wd_cancel (WDOG_ID wdog);
</pre>
<p>
@ -2419,7 +2419,7 @@ level.
<p>
<b>Assumptions/Limitations:</b>
<p>
<b> POSIX Compatibility:</b> This is a NON-POSIX interface.
<b>POSIX Compatibility:</b> This is a NON-POSIX interface.
VxWorks provides the following comparable interface:
<pre>
STATUS wdCancel (WDOG_ID wdog);
@ -7392,7 +7392,6 @@ interface include:
<li>pid_t
<li>size_t
<li>sigset_t
<li>STATUS
<li>time_t
</ul>