Michael Scott 6575e84002 logging: start log processing thread in enable_logger() ... Currently, if CONFIG_LOG_PROCESS_THREAD is enabled, log processing does not start until just before the main() function is called in the user sample. This means that no real-time logging information will be sent to the backends while drivers and/or other processes which are triggered during kernel boot are processing their tasks. Worse, if they take a longish time to finish, the user is presented with a blank log backend regardless of the debug levels. Let's start processing logs earlier to avoid this issue. NOTE: Since this thread is now triggered specifically rather than started during static thread init, let's also name it. Signed-off-by: Michael Scott <mike@foundries.io>		2018-11-07 14:39:55 +02:00
..
CMakeLists.txt	logger: Add a Segger RTT backend	2018-10-31 12:47:53 +01:00
Kconfig	doc: fix kconfig misspellings	2018-11-02 17:58:16 -04:00
Kconfig.template.log_config	logging: make LOG_LEVEL depend on LOG	2018-11-02 15:31:44 -05:00
log_backend_native_posix.c	logging: Add autostart option to LOG_BACKEND_DEFINE	2018-10-11 13:29:50 +03:00
log_backend_rtt.c	logger: rtt backend don't let starve others in blocking mode	2018-11-02 12:24:05 -04:00
log_backend_uart.c	logging: Add autostart option to LOG_BACKEND_DEFINE	2018-10-11 13:29:50 +03:00
log_cmds.c	shell: examples unification	2018-10-19 13:35:56 +02:00
log_core.c	logging: start log processing thread in enable_logger()	2018-11-07 14:39:55 +02:00
log_list.c	logging: subsystem major redesign	2018-06-29 10:16:45 +02:00
log_list.h	logging: subsystem major redesign	2018-06-29 10:16:45 +02:00
log_msg.c	logging: Fix possible out-of-bound access in log_output	2018-10-30 15:29:28 +01:00
log_output.c	subsys: logging: Fix switch statement	2018-11-06 16:20:15 -05:00
sys_log.c	…
sys_log_net.c	…