summaryrefslogtreecommitdiff
path: root/nuttx/drivers/Kconfig
diff options
context:
space:
mode:
authorpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-08-02 00:42:46 +0000
committerpatacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3>2012-08-02 00:42:46 +0000
commit9bc6eb085a6a91f0e6fbd74ad98c3b1d32df0bc4 (patch)
treef5f5fb874369d5379c1bdd728e0789c499e7ce81 /nuttx/drivers/Kconfig
parent2dfc5da16f3e3abc4b36413e8205e3dcd4df7928 (diff)
downloadpx4-nuttx-9bc6eb085a6a91f0e6fbd74ad98c3b1d32df0bc4.tar.gz
px4-nuttx-9bc6eb085a6a91f0e6fbd74ad98c3b1d32df0bc4.tar.bz2
px4-nuttx-9bc6eb085a6a91f0e6fbd74ad98c3b1d32df0bc4.zip
Move RAMLOG driver to drivers/syslog; Add ability to output debug information to any character device or file
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4996 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/drivers/Kconfig')
-rw-r--r--nuttx/drivers/Kconfig68
1 files changed, 4 insertions, 64 deletions
diff --git a/nuttx/drivers/Kconfig b/nuttx/drivers/Kconfig
index 17f471bee..6d4c5fc6a 100644
--- a/nuttx/drivers/Kconfig
+++ b/nuttx/drivers/Kconfig
@@ -29,70 +29,6 @@ config RAMDISK
a block driver that can be mounted as a files system. See
include/nuttx/ramdisk.h.
-config RAMLOG
- bool "RAM log message support"
- default n
- ---help---
- This is a driver that was intended to support debugging output,
- aka syslogging, when the normal serial output is not available.
- For example, if you are using a telnet or USB serial console,
- the debug output will get lost.
-
- This driver is similar to a pipe in that it saves the debugging
- output in a FIFO in RAM. It differs from a pipe in numerous
- details as needed to support logging.
-
-if RAMLOG
-config RAMLOG_SYSLOG
- bool "Use RAMLOG for SYSLOG"
- default n
- depends on SYSLOG
- ---help---
- Use the RAM logging device for the syslogging interface. If this feature
- is enabled (along with SYSLOG), 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.
-
-config RAMLOG_CONSOLE
- bool "Use RAMLOG for /dev/console"
- default n
- depends on DEV_CONSOLE
- ---help---
- Use the RAM logging device as a system console. If this feature is enabled (along
- with DEV_CONSOLE), 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.
-
-config RAMLOG_CONSOLE_BUFSIZE
- int "RAMLOG buffer size"
- default 1024
- depends on RAMLOG_SYSLOG || RAMLOG_CONSOLE
- ---help---
- Size of the console RAM log. Default: 1024
-
-config RAMLOG_CRLF
- bool "RAMLOG CR/LF"
- default n
- ---help---
- Pre-pend a carriage return before every linefeed that goes into the RAM log.
-
-config RAMLOG_NONBLOCKING
- bool "RAMLOG non-block reads"
- default y
- ---help---
- Reading from the RAMLOG will never block if the RAMLOG is empty. If the RAMLOG
- is empty, then zero is returned (usually interpreted as end-of-file).
-
-config RAMLOG_NPOLLWAITERS
- int "RAMLOG number of poll waiters"
- default 4
- depends on !DISABLE_POLL
- ---help---
- The maximum number of threads that may be waiting on the poll method.
-
-endif
-
config CAN
bool "CAN support"
default n
@@ -387,3 +323,7 @@ menuconfig WIRELESS
if WIRELESS
source drivers/wireless/Kconfig
endif
+
+source drivers/syslog/Kconfig
+
+