configs/us7032evb1/ostest: Configuration converted to use the kconfig-frontends tools

configs/Kconfig

@@ -764,6 +764,7 @@ config ARCH_BOARD_US7032EVB1
 	bool "Hitachi SH-1/US7032EVB1 board"
 	depends on ARCH_CHIP_SH7032
 	select ARCH_HAVE_LEDS
+	select ARCH_HAVE_BUTTONS
 	---help---
 		This is a port of the Hitachi SH-1 on the Hitachi SH-1/US7032EVB1 board.
 		STATUS:  Work has just began on this port.

configs/us7032evb1/README.txt

@@ -6,7 +6,7 @@ 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 limit SH-1 support
+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.
@@ -55,30 +55,51 @@ shterm
 Configurations
 ^^^^^^^^^^^^^^
 
-Each SH-1 configuration is maintained in a sub-directory and
+Common Configuration Notes
-can be selected as follow:
+--------------------------
 
-	cd tools
+  1. Each SH-1 configuration is maintained in a sub-directory and
-	./configure.sh us7032evb1/<subdir>
+     can be selected as follow:
-	cd -
-	. ./setenv.sh
 
-Where <subdir> is one of the following:
+       cd tools
+       ./configure.sh us7032evb1/<subdir>
+       cd -
+       . ./setenv.sh
 
-ostest
+     Where <subdir> is one of the configuration sub-directories described in
-^^^^^^as advertised.  This could be a silicon problem, some pipeline issue that is not handled properly by the gcc 3.4.5 tool
+     the following paragraph.
 
-This configuration directory, performs a simple OS test using
+  2. These configurations use the mconf-based configuration tool.  To
-examples/ostest.
+     change a configurations using that tool, you should:
 
-nsh
+     a. Build and install the kconfig-mconf tool.  See nuttx/README.txt
-^^^
+        and misc/tools/
 
-Configures the NuttShell (nsh) located at examples/nsh.  The
+     b. Execute 'make menuconfig' in nuttx/ in order to start the
-Configuration enables only the serial NSH interfaces.
+        reconfiguration process.
 
-NOTE:  At present, the NSH example does not run.  See the "Status"
+  3. By default, all configurations assume the NuttX Buildroot toolchain
-discussion above for a full explanation.
+     under Linux (should work under Windows with Cygwin as well).  This
+     is easily reconfigured:
+
+        CONFIG_HOST_LINUX=y
+        CONFIG_ARM_TOOLCHAIN_BUILDROOT=y
+
+Configuration Sub-Directories
+-----------------------------
+
+  ostest
+
+    This configuration directory, performs a simple OS test using
+    examples/ostest.
+
+  nsh
+
+    Configures the NuttShell (nsh) located at examples/nsh.  The
+    Configuration enables only the serial NSH interfaces.
+
+    NOTE:  At present, the NSH example does not run.  See the "Status"
+    discussion above for a full explanation.
 
 Configuration Options
 ^^^^^^^^^^^^^^^^^^^^^

configs/us7032evb1/ostest/appconfig

@@ -1,39 +0,0 @@
-############################################################################
-# configs/us7032evb1/ostest/appconfig
-#
-#   Copyright (C) 2011 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/ostest
-