diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html index 00b100abb00..bbe8fb6b518 100644 --- a/Documentation/NuttX.html +++ b/Documentation/NuttX.html @@ -8,7 +8,7 @@

NuttX RTOS

-

Last Updated: December 5 2009

+

Last Updated: December 13, 2009

@@ -1616,6 +1616,11 @@ nuttx-2010.1 2010-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> 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 <spudmonkey@racsa.co.cr> diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html index de45bf743dd..a7880d8f8d2 100644 --- a/Documentation/NuttxPortingGuide.html +++ b/Documentation/NuttxPortingGuide.html @@ -438,8 +438,10 @@
  • arch/arm/include/lpc214x and arch/arm/src/lpc214x: 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.
  • @@ -700,7 +702,14 @@
  • configs/us7032evb1: 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.
  • configs/xtrs: diff --git a/Documentation/NuttxUserGuide.html b/Documentation/NuttxUserGuide.html index 3a3eafe3ea8..5d477c8cfc3 100644 --- a/Documentation/NuttxUserGuide.html +++ b/Documentation/NuttxUserGuide.html @@ -13,7 +13,7 @@

    NuttX Operating System

    User's Manual

    by

    Gregory Nutt

    -

    Last Updated: May 22, 2009

    +

    Last Updated: December 13, 2009

    @@ -296,8 +296,8 @@ VxWorks provides the following similar interface: Function Prototype:
        #include <sched.h>
    -   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[]);
     

    @@ -368,7 +368,7 @@ VxWorks provides the following similar interface: Function Prototype:

         #include <sched.h>
    -    STATUS task_activate( _TCB *tcb );
    +    int task_activate( _TCB *tcb );
     

    @@ -418,7 +418,7 @@ the pointer to the WIND_TCB cast to an integer. Function Prototype:

         #include <sched.h>
    -    STATUS task_delete( pid_t pid );
    +    int task_delete( pid_t pid );
     

    @@ -514,7 +514,7 @@ And the UNIX interface: Function Prototype:

         #include <sched.h>
    -    STATUS task_restart( pid_t pid );
    +    int task_restart( pid_t pid );
     

    @@ -974,7 +974,7 @@ priority of the calling task is returned. Function Prototype:

         #include <sched.h>
    -    STATUS sched_lock( void );
    +    int sched_lock( void );
     

    @@ -994,7 +994,7 @@ number of times) or until it blocks itself.

    Assumptions/Limitations:

    - POSIX Compatibility: This is a NON-POSIX interface. +POSIX Compatibility: This is a NON-POSIX interface. VxWorks provides the comparable interface:

         STATUS taskLock( void );
    @@ -1006,7 +1006,7 @@ VxWorks provides the comparable interface:
     Function Prototype: 
     
         #include <sched.h>
    -    STATUS sched_unlock( void );
    +    int sched_unlock( void );
     

    @@ -1027,7 +1027,7 @@ eligible to preempt the current task will execute.

    Assumptions/Limitations:

    - POSIX Compatibility: This is a NON-POSIX interface. +POSIX Compatibility: This is a NON-POSIX interface. VxWorks provides the comparable interface:

         STATUS taskUnlock( void );
    @@ -2296,7 +2296,7 @@ initialization time).
     Function Prototype: 
     
         #include <wdog.h>
    -    STATUS wd_delete (WDOG_ID wdog);
    +    int wd_delete (WDOG_ID wdog);
     

    @@ -2321,7 +2321,7 @@ pointer to a watchdog structure. caller to assure that the watchdog is inactive before deleting it.

    - POSIX Compatibility: This is a NON-POSIX interface. +POSIX Compatibility: This is a NON-POSIX interface. VxWorks provides the following comparable interface:

         STATUS wdDelete (WDOG_ID wdog);
    @@ -2340,7 +2340,7 @@ before deallocating it (i.e., never returns ERROR).
     Function Prototype: 
     
         #include <wdog.h>
    -    STATUS wd_start( WDOG_ID wdog, int delay, wdentry_t wdentry,
    +    int wd_start( WDOG_ID wdog, int delay, wdentry_t wdentry,
                          intt argc, ....);
     
    @@ -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.

    - POSIX Compatibility: This is a NON-POSIX interface. +POSIX Compatibility: This is a NON-POSIX interface. VxWorks provides the following comparable interface:

         STATUS wdStart (WDOG_ID wdog, int delay, FUNCPTR wdentry, int parameter);
    @@ -2397,7 +2397,7 @@ number of parameters is determined by
     Function Prototype: 
     
         #include <wdog.h>
    -    STATUS wd_cancel (WDOG_ID wdog);
    +    int wd_cancel (WDOG_ID wdog);
     

    @@ -2419,7 +2419,7 @@ level.

    Assumptions/Limitations:

    - POSIX Compatibility: This is a NON-POSIX interface. +POSIX Compatibility: This is a NON-POSIX interface. VxWorks provides the following comparable interface:

         STATUS wdCancel (WDOG_ID wdog);
    @@ -7392,7 +7392,6 @@ interface include:
     
  • pid_t
  • size_t
  • sigset_t -
  • STATUS
  • time_t