cc528d37c2
The immediate logging option cannot be used with network logging support CONFIG_LOG_BACKEND_NET as that would cause the generated rsyslog messages to be malformed. The UDP packets would only have one byte payloads which is not correct. So make sure that user is not able to select a configuration with immediate mode and network logging. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
42 lines
1.0 KiB
Plaintext
42 lines
1.0 KiB
Plaintext
CONFIG_NETWORKING=y
|
|
CONFIG_NET_UDP=y
|
|
CONFIG_ENTROPY_GENERATOR=y
|
|
CONFIG_TEST_RANDOM_GENERATOR=y
|
|
CONFIG_INIT_STACKS=y
|
|
CONFIG_NET_PKT_RX_COUNT=32
|
|
CONFIG_NET_PKT_TX_COUNT=32
|
|
CONFIG_NET_BUF_RX_COUNT=32
|
|
CONFIG_NET_BUF_TX_COUNT=32
|
|
|
|
CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=3
|
|
CONFIG_NET_IF_MCAST_IPV6_ADDR_COUNT=5
|
|
|
|
CONFIG_NET_LOG=y
|
|
CONFIG_LOG=y
|
|
|
|
# Immediate logging does not work with network syslog as it would cause
|
|
# the sent packet to be malformed (contains only 1 byte data)
|
|
CONFIG_LOG_IMMEDIATE=n
|
|
CONFIG_LOG_PROCESS_THREAD=y
|
|
|
|
CONFIG_NET_IPV6=y
|
|
CONFIG_NET_IPV4=y
|
|
CONFIG_NET_DHCPV4=n
|
|
|
|
CONFIG_NET_SHELL=y
|
|
|
|
CONFIG_NET_CONFIG_SETTINGS=y
|
|
CONFIG_NET_CONFIG_NEED_IPV6=y
|
|
CONFIG_NET_CONFIG_NEED_IPV4=y
|
|
CONFIG_NET_CONFIG_MY_IPV6_ADDR="2001:db8::1"
|
|
CONFIG_NET_CONFIG_PEER_IPV6_ADDR="2001:db8::2"
|
|
CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.1"
|
|
CONFIG_NET_CONFIG_PEER_IPV4_ADDR="192.0.2.2"
|
|
|
|
# logging net backend config
|
|
CONFIG_LOG_BACKEND_NET=y
|
|
CONFIG_LOG_BACKEND_NET_SERVER="[2001:db8::2]:514"
|
|
|
|
# Get newlib by default as it has proper time function support
|
|
CONFIG_NEWLIB_LIBC=y
|