configs/ez80f910200zco/nsh: Configuration converted to use the kconfig-frontends tools

ChangeLog

@@ -6837,3 +6837,5 @@
 	  kconfig-frontends tools (2014-3-4)
 	* configs/sim/nx11: Configuration converted to use the
 	  kconfig-frontends tools (2014-3-4)
+	* configs/ez80f910200zco/nsh: Configuration converted to use the
+	  kconfig-frontends tools (2014-3-4)

configs/eagle100/README.txt

@@ -346,15 +346,31 @@ Eagle100-specific Configuration Options
 Configurations
 ^^^^^^^^^^^^^^
 
-Each Eagle-100 configuration is maintained in a sub-directory and
+Common Configuration Notes
-can be selected as follow:
+--------------------------
 
-    cd tools
+  1. Each Eagle-100 configuration is maintained in a sub-directory and
-    ./configure.sh eagle100/<subdir>
+     can be selected as follow:
-    cd -
-    . ./setenv.sh
 
-Where <subdir> is one of the following:
+       cd tools
+       ./configure.sh eagle100/<subdir>
+       cd -
+       . ./setenv.sh
+
+     Where <subdir> is one of the configuration sub-directories described in
+     the following paragraph.
+
+  2. These configurations use the mconf-based configuration tool.  To
+     change a configurations using that tool, you should:
+
+     a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
+        and misc/tools/
+
+     b. Execute 'make menuconfig' in nuttx/ in order to start the
+        reconfiguration process.
+   
+Configuration Sub-Directories
+-----------------------------
 
   nettest:
     This configuration directory may be used to enable networking using the
@@ -363,16 +379,7 @@ Where <subdir> is one of the following:
 
     NOTES:
 
-    1. This configuration uses the mconf-based configuration tool.  To
+    1. This configuration is set to use Cygwin under Windows and the
-       change this configurations using that tool, you should:
-
-       a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-          and misc/tools/
-
-       b. Execute 'make menuconfig' in nuttx/ in order to start the
-          reconfiguration process.
-
-    2. This configuration is set to use Cygwin under Windows and the
        CodeSourcery toolchain.  That, however, is easily reconfigurable:
 
          CONFIG_HOST_WINDOWS=y
@@ -385,16 +392,7 @@ Where <subdir> is one of the following:
 
     NOTES:
 
-    1. This configuration uses the mconf-based configuration tool.  To
+    1. This configuration is set to use Cygwin under Windows and the
-       change this configurations using that tool, you should:
-
-       a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-          and misc/tools/
-
-       b. Execute 'make menuconfig' in nuttx/ in order to start the
-          reconfiguration process.
-
-    2. This configuration is set to use Cygwin under Windows and the
        CodeSourcery toolchain.  That, however, is easily reconfigurable:
 
          CONFIG_HOST_WINDOWS=y
@@ -412,16 +410,7 @@ Where <subdir> is one of the following:
 
     NOTES:
 
-    1. This configuration uses the mconf-based configuration tool.  To
+    1. This configuration is set to use Cygwin under Windows and the
-       change this configurations using that tool, you should:
-
-       a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-          and misc/tools/
-
-       b. Execute 'make menuconfig' in nuttx/ in order to start the
-          reconfiguration process.
-
-    4. This configuration is set to use Cygwin under Windows and the
        devkitARM toolchain.  That, however, is easily reconfigurable:
 
        CONFIG_HOST_WINDOWS=y
@@ -433,19 +422,10 @@ Where <subdir> is one of the following:
 
     NOTES:
 
-    1. This configuration uses the mconf-based configuration tool.  To
+    1. This example can only be built using the NuttX buildroot
-       change this configurations using that tool, you should:
-
-       a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-          and misc/tools/
-
-       b. Execute 'make menuconfig' in nuttx/ in order to start the
-          reconfiguration process.
-
-    2. This example can only be built using the NuttX buildroot
        toolchain with the NXFLAT tools.
 
-    3. This configuration is set to use Cygwin under Windows and the
+    2. This configuration is set to use Cygwin under Windows and the
        devkitARM toolchain.  That, however, is easily reconfigurable:
 
        CONFIG_HOST_WINDOWS=y
@@ -458,16 +438,7 @@ Where <subdir> is one of the following:
 
     NOTES:
 
-    1. This configuration uses the mconf-based configuration tool.  To
+    1. This configuration is set to use Linux and the buildroot toolchain.
-       change this configurations using that tool, you should:
-
-       a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-          and misc/tools/
-
-       b. Execute 'make menuconfig' in nuttx/ in order to start the
-          reconfiguration process.
-
-    2. This configuration is set to use Linux and the buildroot toolchain.
        That, however, is easily reconfigurable:
 
          CONFIG_HOST_LINUX=y
@@ -476,8 +447,8 @@ Where <subdir> is one of the following:
        This example can only be built using the buildroot toolchain
        with NXFLAT support
 
-By default, all of these examples are built to be used with the Luminary
+  By default, all of these examples are built to be used with the Luminary
-Ethernet Bootloader (you can change the ld.script file in any of these
+  Ethernet Bootloader (you can change the ld.script file in any of these
-sub-directories to change that configuration).
+  sub-directories to change that configuration).
 
 

configs/ez80f910200zco/README.txt

@@ -17,7 +17,7 @@ Version 4.11.0
   The 5.1.1 version of the ZDS-II tools are currently configured for
   all ez80 boards.  However, it is the older version 4.11.0 that this code
   has been verified against.
-  
+
   Although it compiles without error, the 4.11.0 compiler generates
   bad code on one of the files, mm/mm_initialize.c.  Below is a simple work-
   around.
@@ -27,12 +27,12 @@ Version 4.11.0
     @@ -94,8 +94,11 @@
     {
        int i;
- 
+
     +#if 0 /* DO NOT CHECK IN */
        CHECK_ALLOCNODE_SIZE;
        CHECK_FREENODE_SIZE;
     +#endif
- 
+
    /* Set up global variables */
 
    UPDATE:  I don't know if 4.11.1 has this same problem (I bet not since
@@ -52,87 +52,73 @@ Version 5.1.1
   to modify the versioning in Make.defs and setenv.sh; if you want to build
   on a different platform, you will need to change the path in the ZDS binaries
   in those same files.
-  
+
 Other Versions
   If you use any version of ZDS-II other than 5.1.1 or if you install ZDS-II
   at any location other than the default location, you will have to modify
   two files:  (1) configs/ez80f910200kitg/*/setenv.sh and (2)
   configs/ez80f910200kitg/*/Make.defs.
 
+Configurations
+^^^^^^^^^^^^^^
+
+Common Configuration Notes
+--------------------------
+
+  1. src/ and include/
+
+     These directories contain common logic for all ez80f910200zco
+     configurations.
+
+  2. Variations on the basic ez80f910200zco configuration are maintained
+     in subdirectories.  To configure any specific configuration, do the
+     following steps:
+
+       cd <nuttx-top-directory>/tools
+       ./configure.sh ez80f910200zco/<sub-directory>
+       cd <nuttx-top-directgory>
+       make
+
+     Where <sub-directory> is the specific board configuration that you
+     wish to build.  The available board-specific configurations are
+     summarized in the following paragraph.
+
+     Use configure.bat instead of configure.sh if you are building in a
+     native Windows environment.
+
+  3. This configuration uses the mconf-based configuration tool.  To
+     change this configurations using that tool, you should:
+
+     a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
+        and misc/tools/
+
+     b. Execute 'make menuconfig' in nuttx/ in order to start the
+        reconfiguration process.
+
 Configuration Subdirectories
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+----------------------------
 
-src/ and include/
+  dhcpd:
-    These directories contain common logic for all ez80f910200zco
-    configurations.
-
-Variations on the basic ez80f910200zco configuration are maintained
-in subdirectories.  To configure any specific configuration, do the
-following steps:
-
-   cd <nuttx-top-directory>/tools
-   ./configure.sh ez80f910200zco/<sub-directory>
-   cd <nuttx-top-directgory>
-   make
-
-Where <sub-directory> is the specific board configuration that you
-wish to build.  The following board-specific configurations are
-available:
-
-dhcpd:
     This builds the DCHP server using the examples/dhcpd application
     (for execution from FLASH.) See apps/examples/README.txt for information
     about the dhcpd example.
 
-    NOTES:
+  httpd:
-
-    1. This configuration uses the mconf-based configuration tool.  To
-       change this configurations using that tool, you should:
-
-       a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-          and misc/tools/
-
-       b. Execute 'make menuconfig' in nuttx/ in order to start the
-          reconfiguration process.
-
-httpd:
     This builds the uIP web server example using the examples/uip application
     (for execution from FLASH). See apps/examples/README.txt for information
     about httpd.
 
-    NOTES:
+  nsh:
-
-    1. This configuration uses the mconf-based configuration tool.  To
-       change this configurations using that tool, you should:
-
-       a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-          and misc/tools/
-
-       b. Execute 'make menuconfig' in nuttx/ in order to start the
-          reconfiguration process.
-
-nsh
     This configuration builds the NuttShell (NSH).  That code can be
     found in examples/nsh.  For more information see:  examples/nsh/README.txt
     and Documentation/NuttShell.html.
 
-nettest
+  nettest:
     This configuration is used for testing the eZ80F91 EMAC driver.  It
     builds examples/nettest.  See examples/README.txt for more information
     about nettest.
 
-    NOTES:
+  poll:
-
-    1. This configuration uses the mconf-based configuration tool.  To
-       change this configurations using that tool, you should:
-
-       a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-          and misc/tools/
-
-       b. Execute 'make menuconfig' in nuttx/ in order to start the
-          reconfiguration process.
-
-poll
     This configuration is also used for testing the eZ80F91 EMAC driver.  It
     builds examples/poll.  See examples/README.txt for more information
     about the poll test.

configs/ez80f910200zco/nsh/appconfig

@@ -1,55 +0,0 @@
-############################################################################
-# configs/ez80f910200zco/nsh/appconfig
-#
-#   Copyright (C) 2011-2012 Gregory Nutt. All rights reserved.
-#   Author: Gregory Nutt <gnutt@nuttx.org>
-#
-# Redistribution and use in source and binary forms, with or without
-# modification, are permitted provided that the following conditions
-# are met:
-#
-# 1. Redistributions of source code must retain the above copyright
-#    notice, this list of conditions and the following disclaimer.
-# 2. Redistributions in binary form must reproduce the above copyright
-#    notice, this list of conditions and the following disclaimer in
-#    the documentation and/or other materials provided with the
-#    distribution.
-# 3. Neither the name NuttX nor the names of its contributors may be
-#    used to endorse or promote products derived from this software
-#    without specific prior written permission.
-#
-# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
-# FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
-# COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
-# INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
-# BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
-# OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
-# AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
-# LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
-# ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
-# POSSIBILITY OF SUCH DAMAGE.
-#
-############################################################################
-
-# Path to example in apps/examples containing the user_start entry point
-
-CONFIGURED_APPS += examples/nsh
-
-# NSH library
-
-CONFIGURED_APPS += system/readline
-CONFIGURED_APPS += nshlib
-
-# Networking support
-
-ifeq ($(CONFIG_NET),y)
-CONFIGURED_APPS += netutils/uiplib
-CONFIGURED_APPS += netutils/dhcpc
-CONFIGURED_APPS += netutils/resolv
-CONFIGURED_APPS += netutils/tftpc
-CONFIGURED_APPS += netutils/webclient
-endif
-
-