Fix some typos and compilation errors introduced in the last checkin

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4384 42af7a65-404d-4744-a932-0658087f49c3

1 files changed, 20 insertions, 3 deletions

diff --git a/nuttx/configs/stm3240g-eval/README.txt b/nuttx/configs/stm3240g-eval/README.txt
index 727b46d08..ef26c0088 100755
--- a/nuttx/configs/stm3240g-eval/README.txt
+++ b/nuttx/configs/stm3240g-eval/README.txt
@@ -694,9 +694,26 @@ Where <subdir> is one of the following:
     -CONFIG_STM32_SDIO=n        : SDIO is enabled
     +CONFIG_STM32_SDIO=y
 
-    Logically, that is the only difference.  There are, however, other configuration
-    differences as necessary to support this different device configuration. Just
-    the do the 'diff' if you are curious.
+    Logically, that is the only difference:  This configuration has SDIO (and
+    the SD card) enabled and the serial console disabled. There is ONLY a
+    Telnet console!.
+    
+    There are some special settings to make life with only a Telnet 
+
+    CONFIG_SYSLOG=y - Enables the System Logging feature.
+    CONFIG_RAMLOG=y - Enable the RAM-based logging feature.
+    CONFIG_RAMLOG_CONSOLE=y - Use the RAM logger as the default console.
+      This means that any console output from non-Telnet threads will
+      go into the circular buffer in RAM.
+    CONFIG_RAMLOG_SYSLOG - This enables the RAM-based logger as the
+      system logger.  This means that (1) in addition to the console
+      output from other tasks, ALL of the debug output will also to
+      to the circular buffer in RAM, and (2) NSH will now support a
+      command called 'dmesg' that can be used to dump the RAM log.
+
+    There are a few other configuration differences as necessary to support
+    this different device configuration. Just the do the 'diff' if you are
+    curious.
 
     NOTES:
     1. See the notes for the nsh configuration.  Most also apply to the nsh2