diff --git a/Documentation/NuttX.html b/Documentation/NuttX.html index 224b1bef81..5721c5eff2 100644 --- a/Documentation/NuttX.html +++ b/Documentation/NuttX.html @@ -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: March 30, 2011</p> + <p>Last Updated: April 3, 2011</p> </td> </tr> </table> @@ -2188,11 +2188,28 @@ nuttx-6.1 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> * syscall/: The beginnings of an optional syscall kernel interface. * tools/mksyscall.c: Add a tool that will auto-generate syscall proxies and stubs from a comma-separated-value (CSV) data file. + * arch/arm/src/cortexm3/mpu.h: Add a header file describing the Cortex-M3 + MPU registers. + * Numerous modifications to the build system. Various people have reported + build problems since the re-organization and release of NuttX-6.0. I am + unable to replicate the build problems in my environment, but the changes + have be incorporated in hope of correcting the build issues in other + environments. + * drivers/i2c/st_lis331dl.c: I2C-based driver for the LIS331DL MEMS + motion sensor. Contributed by Uros Platise. + * Makefile: The NuttX build system will now supported building NuttX as two + separately linked images: (1) a kernel-mode RTOS image, and (2) a user- + mode application image that communicates to the RTOS kernel via system + calls. A lot more still must be done. apps-6.1 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> * Creation of auto-generated header files now occurs during the context build phase. + * Added sdcard insert and eject, nsh command '?' and some code remarks + * Renamed nuttapp to namedapp + * namedapp/binfs.c -- Create a tiny filesystem that can be used + to show the internal named apps under /bin. pascal-2.1 2011-xx-xx Gregory Nutt <spudmonkey@racsa.co.cr> diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html index ef444506f5..eaa603a4a1 100644 --- a/Documentation/NuttxPortingGuide.html +++ b/Documentation/NuttxPortingGuide.html @@ -12,7 +12,7 @@ <h1><big><font color="#3c34ec"> <i>NuttX RTOS Porting Guide</i> </font></big></h1> - <p>Last Updated: April 1, 2011</p> + <p>Last Updated: April 3, 2011</p> </td> </tr> </table> @@ -2034,7 +2034,7 @@ extern void up_ledoff(int led); <ul> <li> <p> - <b><code>include/nuttx/i2c.h</code></b>. + <b><code>include/nuttx/i2c/i2c.h</code></b>. All structures and APIs needed to work with I2C drivers are provided in this header file. </p> </li> @@ -2790,7 +2790,7 @@ build Two-pass Build Options. If the 2 pass build option is selected, then these options configure the make system build a extra link object. This link object is assumed to be an incremental (relative) link object, but could be a static library (archive) - (some modification to this Makefile would be required if CONFIG_PASS1_OBJECT is an archive). + (some modification to this Makefile would be required if CONFIG_PASS1_TARGET generates an archive). Pass 1 1ncremental (relative) link objects should be put into the processor-specific source directory where other link objects will be created - ff the pass1 obect is an archive, it could go anywhere. </p> @@ -2805,15 +2805,27 @@ build </p> <ul> <li> - <code>CONFIG_PASS1_OBJECT</code>: The name of the first pass object. + <p> + <code>CONFIG_PASS1_TARGET</code>: The name of the first pass build target. + </p> </li> <li><code>CONFIG_PASS1_BUILDIR</code>: - The path, relative to the top NuttX build directory to directory that contains the Makefile to build the first pass object. - The Makefile must support the following targets: - <ul> - <li>The special target <code>arch/$(CONFIG_ARCH)/src/$(CONFIG_PASS1_OBJECT)</code>, and</li> - <li>The usual depend, clean, and distclean targets.</li> - </ul> + <p> + The path, relative to the top NuttX build directory to directory that contains the Makefile to build the first pass object. + The Makefile must support the following targets: + </p> + <p> + <ul> + <li>The special target <code>CONFIG_PASS1_TARGET</code> (if defined), and</li> + <li>The usual depend, clean, and distclean targets.</li> + </ul> + </p> + </li> + <li> + <code>CONFIG_PASS1_OBJECT</code>: May be used to include an extra, pass1 object into the final link. + This would probably be the object generated from the <code>CONFIG_PASS1_TARGET</code>. + It may be available at link time in the <code>arch/<architecture>/src</code> directory. + </li> </ul> <h2>General OS setup</h2>