summaryrefslogtreecommitdiff
path: root/nuttx/Documentation
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-02-11 14:20:40 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-02-11 14:20:40 +0000
commit75e67f05d4b97efc32d95b478ec1c1f959992a4b (patch)
tree8cf471347f767130a152b249bafd7de1a6017757 /nuttx/Documentation
parent4a62de545bf87610c2415218e144ddef4dd0e75c (diff)
downloadpx4-nuttx-75e67f05d4b97efc32d95b478ec1c1f959992a4b.tar.gz
px4-nuttx-75e67f05d4b97efc32d95b478ec1c1f959992a4b.tar.bz2
px4-nuttx-75e67f05d4b97efc32d95b478ec1c1f959992a4b.zip
Add logic to re-direct debug output to a sysloggin device
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4381 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/Documentation')
-rw-r--r--nuttx/Documentation/NuttxPortingGuide.html43
1 files changed, 43 insertions, 0 deletions
diff --git a/nuttx/Documentation/NuttxPortingGuide.html b/nuttx/Documentation/NuttxPortingGuide.html
index 244f07538..4b562057d 100644
--- a/nuttx/Documentation/NuttxPortingGuide.html
+++ b/nuttx/Documentation/NuttxPortingGuide.html
@@ -3942,6 +3942,49 @@ build
</ul>
<p>
+ System Logging:
+</p>
+<ul>
+ <li>
+ <code>CONFIG_SYSLOG</code>: Enables general system logging support.
+ </li>
+ <p>
+ At present, the only system loggin device is a circular buffer in RAM.
+ If <code>CONFIG_SYSLOG</code> is selected, then these options are also available.
+ </p>
+ <li>
+ <code>CONFIG_RAMLOG</code>: Enables the RAM logging feature
+ </li>
+ <li>
+ <code>CONFIG_RAMLOG_CONSOLE</code>: Use the RAM logging device as a system console.
+ If this feature is enabled (along with <code>CONFIG_DEV_CONSOLE</code>), then all
+ console output will be re-directed to a circular buffer in RAM. This
+ is useful, for example, if the only console is a Telnet console. Then
+ in that case, console output from non-Telnet threads will go to the
+ 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.
+ </li>
+ <li>
+ <code>CONFIG_RAMLOG_NPOLLWAITERS</code>: The number of threads than can be waiting
+ for this driver on poll(). Default: 4
+ </li>
+ <p>
+ If <code>CONFIG_RAMLOG_CONSOLE</code> or <code>CONFIG_RAMLOG_SYSLOG</code> is selected, then the
+ following may also be provided:
+ </p>
+ </li>
+ <li>
+ <code>CONFIG_RAMLOG_CONSOLE_BUFSIZE</code>: Size of the console RAM log. Default: 1024
+ </li>
+</ul>
+
+<p>
Kernel build options:
</p>
<ul>