Fix syslog mutual exclusion and interrupt level logic

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

1 files changed, 6 insertions, 5 deletions

diff --git a/nuttx/Documentation/NuttxPortingGuide.html b/nuttx/Documentation/NuttxPortingGuide.html
index 21212a386..893522358 100644
--- a/nuttx/Documentation/NuttxPortingGuide.html
+++ b/nuttx/Documentation/NuttxPortingGuide.html
@@ -4101,6 +4101,7 @@ build
   <li>
     <code>CONFIG_SYSLOG_CHAR</code>:
       Enable the generic character device for the SYSLOG.
+      A disadvantage of using the generic character device for the SYSLOG is that it cannot handle debug output generated from interrupt level handlers.
       NOTE:  No more than one SYSLOG device should be configured.
   <p>
     Alternatively, a circular buffer in RAM can be used as the SYSLOGing device.
@@ -4118,11 +4119,11 @@ build
     circular buffer and can be viewed using the NSH 'dmesg' command.
   </li>
   <li>
-    <code>CONFIG_RAMLOG_SYSLOG</code>: Use the RAM logging device for the syslogging
-    interface.  If this feature is enabled (along with <code>CONFIG_SYSLOG</code>),
-    then all debug output (only) will be re-directed to the circular
-    buffer in RAM.  This RAM log can be view from NSH using the 'dmesg'
-    command.
+    <code>CONFIG_RAMLOG_SYSLOG</code>:
+    Use the RAM logging device for the syslogging interface.
+    If this feature is enabled (along with <code>CONFIG_SYSLOG</code>), then all debug output (only) will be re-directed to the circular buffer in RAM.
+    This RAM log can be view from NSH using the <code>dmesg</code> command.
+    NOTE: Unlike the limited, generic character driver SYSLOG device, the RAMLOG <i>can</i> be used to generate debug output from interrupt level handlers.
   </li>
   <li>
     <code>CONFIG_RAMLOG_NPOLLWAITERS</code>: The number of threads than can be waiting