Merge branch 'master' into nuttx-merge-5447

nuttx/TODO

@@ -1,4 +1,4 @@
-NuttX TODO List (Last updated September 16, 2012)
+NuttX TODO List (Last updated November 25, 2012)
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
 This file summarizes known NuttX bugs, limitations, inconsistencies with 
@@ -20,7 +20,7 @@ nuttx/
   (5)  Graphics subystem (graphics/)
   (1)  Pascal add-on (pcode/)
   (1)  Documentation (Documentation/)
-  (6)  Build system / Toolchains
+  (8)  Build system / Toolchains
   (5)  Linux/Cywgin simulation (arch/sim)
   (6)  ARM (arch/arm/)
   (1)  ARM/C5471 (arch/arm/src/c5471/)
@@ -35,12 +35,12 @@ nuttx/
   (7)  ARM/STM32 (arch/arm/src/stm32/)
   (3)  AVR (arch/avr)
   (0)  Intel x86 (arch/x86)
-  (4)  8051 / MCS51 (arch/8051/)
+  (5)  8051 / MCS51 (arch/8051/)
   (3)  MIPS/PIC32 (arch/mips)
   (1)  Hitachi/Renesas SH-1 (arch/sh/src/sh1)
   (4)  Renesas M16C/26 (arch/sh/src/m16c)
  (10)  z80/z8/ez80 (arch/z80/)
-  (8)  z16 (arch/z16/)
+  (9)  z16 (arch/z16/)
   (1)  mc68hc1x (arch/hc)
 
 apps/
@@ -890,23 +890,30 @@ o Build system
   Description: Need a NuttX configuration tool.  The number of configuration
                settings has become quite large and difficult to manage manually.
                Update:  This task is essentially completed.  But probably not for
-               all platforms and all features.  When do we know that the the
-               features is complete and that we can switch to exclusive use of
-               the tool?
+               all platforms and all features.  When do we know that the feature
+               is complete and that we can switch to exclusive use of the tool?
   Status:      Open
   Priority:    Medium-low
 
   Title:       NATIVE WINDOWS BUILD
-  Description: At present, NuttX builds only under Linux or Cygwin.
-               Investigate the possibility of a native Windows build using
-               something like the GNUWin32 tools (coreutils+make+grep+sed+uname).
+  Description: This effort is underway using MinGW-GCC and GNUWin32 tools
+               for (coreutils+make+grep+sed+uname).  Current status:
+
+               1. configs/stm32f4discovery/winbuild - builds okay natively
+               2. configs/ez80f910200kitg - Can be reconfigured to build natively.
+                  Requires some manual intervention to get a clean build.
+                  See configs/ez80f910200kitg/README.txt.
+
   Status:      Open
   Priority:    Low
 
   Title:       WINDOWS DEPENDENCY GENERATION
   Description: Dependency generation is currently disabled when a Windows native
-               toolchain is used.  I think that the only issue is that all of the
-               Windows dependencies needed to be quoted in the Make.dep files.
+               toolchain is used in a POSIX-like enviornment (like Cygwin).  The
+               issue is that the Windows tool generates dependencies use Windows
+               path formatting and this fails with the dependency file (Make.dep)
+               is include).  Perhaps the only issue is that all of the Windows
+               dependencies needed to be quoted in the Make.dep files.
   Status:      Open
   Priority:    Low -- unless some dependency-related build issues is discovered.
 
@@ -962,6 +969,48 @@ o Build system
   Priority:    Low -- the kernel build configuration is not fully fielded
                yet.
 
+  Title:       mconf NOT AVAILABLE IN NATIVE WINDOWS BUILD
+  Description: NuttX is migrating to the use of the kconfig-frontends mconf
+               tool for all configurations.  In NuttX 6.24, support for native
+               Windows builds was added.  However, the mconf tool does not
+               build to run natively under Windows.
+
+               Some effort was spent trying to get a clean mconf build under
+               Windows.  This is documented in the message thread beginning
+               here: http://tech.groups.yahoo.com/group/nuttx/message/2900.
+               The build was successfully completed using:  MinGW-GCC, MSYS,
+               additional Windows libraries, and additional MSYS libraries
+               (MSYS is a variant of Cygwin so, presumeably, Cygwin could
+               have been used as well).  However, on final testing, it was
+               found that there are problems with text and numeric entry:
+               http://tech.groups.yahoo.com/group/nuttx/message/2953.  This
+               was considered a show stopper and the changs were not checked
+               in.
+
+               Options:  (1) Use conf (not mconf).  confis the text-only
+               configuration tool, (2) fix mconf, (3) write another variant
+               of the configuration tool for windows, or (4) do all configuration
+               under Cygwin or MSYS.  I am doing (4) now, but this is very
+               awkward because I have to set the apps path to ../apps (vs
+               ..\apps) and CONFIG_WINDOWS_NATIVE=n for the 'make menuconfig'
+               to run error free under windows.  Very awkward!
+  Status:      Open, there are some workarounds, but none are good.
+  Priority:    High
+
+  Title:       configure.sh NOT AVAILABLE IN NATIVE WINDOWS BUILD
+  Description: configure.sh is a Bash script and cannot be used from a Windows
+               CMD.exe window.  I started a configure.bat script, but I do
+               not have the batch file programming skills to duplicate some
+               of the more complex operations.
+
+               I also considered adding a configure.c file that could be 
+               compiled and then executed by configure.bat (and configure.sh?).
+               But I have not gone down that path yet.
+
+               The current work-around is to configure under Cygwin.
+  Status:      Open
+  Priority:    High
+
 o Linux/Cywgin simulation (arch/sim)
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
@@ -1507,6 +1556,16 @@ o 8051 / MCS51 (arch/8051/)
   Status:      Open
   Priority:    Low -- only because there as so many other issues with 8051
 
+  Title:       8051 BUILD BROKEN
+  Description: The last time I tried to build the pjrc-8051 configurtion using
+               the SDCC 3.2.1 toolchain (for Windows).  I got compilation
+               errors in sched/os_bringup.c.  It complained about type
+               mis-matches.  What I gather from Googling, this is a problem
+               with the --stack-auto option.  At any rate, this problem will
+               need to be fixed if you want to resurrect the 8051 NuttX port.
+ Status:       Open
+ Priority:     Low -- I don't think anyone uses the 8051 port.
+
 o MIPS/PIC32(arch/mips)
   ^^^^^^^^^^^^^^^^^^^^^
 
@@ -1835,9 +1894,17 @@ o z16 (arch/z16)
                Internal Error(0503) On line 2504 of "MMCSD\MMCSD_SDIO.C"
                    File <c3>, Args(562,46)
 
-  Status:     Open.  Recommended workaround: remove mmcsd_sdio.c from
-              drivers/mmcsd/Make.defs.  There is no SDIO support for the Z16 anyway
-  Priority:   Low
+  Status:      Open.  Recommended workaround: remove mmcsd_sdio.c from
+               drivers/mmcsd/Make.defs.  There is no SDIO support for the Z16 anyway
+  Priority:    Low
+
+  Title:       NATIVE BUILD PROBLEMS
+  Description: When last tested (ca.12/12), there were some missing .obj files in
+               arch/z16/src. A little additional TLC will be needed to get a
+               reliable Windows native build.  As of this writing, the Cygwin
+               based build has not been re-verified.
+  Status:      Open
+  Priority:    Low -- I don't think anyone uses the Z16 port.  
 
 o mc68hc1x (arch/hc)
   ^^^^^^^^^^^^^^^^^^