The initial SYLOG device logic was valiant but yet still not enough

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

1 files changed, 11 insertions, 1 deletions

diff --git a/nuttx/drivers/syslog/README.txt b/nuttx/drivers/syslog/README.txt
index c034b49b6..611f43567 100644
--- a/nuttx/drivers/syslog/README.txt
+++ b/nuttx/drivers/syslog/README.txt
@@ -7,7 +7,17 @@ debug output and, therefore, the syslogging interfaces are defined in the
 header file include/debug.h.
 
 By default, all system log output goes to console (/dev/console).  But that
-behavior can be changed by the drivers in this directory.
+behavior can be changed by the defining CONFIG_SYSLOG in the NuttX
+configuration.  In that, case all low-level debug output will go through
+syslog_putc().
+
+One version of syslog_putc() is defined in fs/fs_syslog.c; that version is
+used when CONFIG_SYSLOG_CHAR is defined.  That version of syslog_putc()
+just integrates with the file system to re-direct debug output to a
+character device or to a file.
+
+If CONFIG_SYSLOG_CHAR is not defined, then other custom SYSLOG drivers
+can be used.  Those custom SYSLOG drivers reside in this directory.
 
 ramlog.c
 --------