OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/net/Kconfig

113 lines
3.4 KiB
Plaintext
Raw Normal View History

drivers: slip: Consolidate under drivers/net/ Make drivers/net/ be the place for misc networking-related drivers (otherwise, we'd need to have a new dir per driver). Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2017-10-21 01:20:01 +08:00
# Kconfig - Misc network drivers configuration options
slip: Add driver for host to qemu connectivity The SLIP driver is using UART pipe driver to communicate with host when Zephyr is running in Qemu. Currently this is only used by networking sub-system when testing the networking stack. Change-Id: I432b4136670766a7fc190f146057924c266f9bea Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-09 17:26:52 +08:00
#
# Copyright (c) 2016 Intel Corporation
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
#
# 1) Redistributions of source code must retain the above copyright notice,
# this list of conditions and the following disclaimer.
#
# 2) Redistributions in binary form must reproduce the above copyright notice,
# this list of conditions and the following disclaimer in the documentation
# and/or other materials provided with the distribution.
#
# 3) Neither the name of Intel Corporation nor the names of its contributors
# may be used to endorse or promote products derived from this software without
# specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
# LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
# POSSIBILITY OF SUCH DAMAGE.
#
#
# SLIP options
#
menuconfig SLIP
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
bool "SLIP driver"
slip: Add driver for host to qemu connectivity The SLIP driver is using UART pipe driver to communicate with host when Zephyr is running in Qemu. Currently this is only used by networking sub-system when testing the networking stack. Change-Id: I432b4136670766a7fc190f146057924c266f9bea Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-09 17:26:52 +08:00
select UART_PIPE
select UART_INTERRUPT_DRIVEN
if SLIP
config SLIP_DRV_NAME
string "SLIP Driver name"
default "slip"
help
This option sets the driver name
config SLIP_MTU
int "SLIP MTU"
slip: Support TAP functionality If CONFIG_SLIP_TAP is defined, then ethernet link layer header is added before the packet. Change-Id: I3d266017f85683999d3c67de49b75b60686d7ba7 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-24 16:19:53 +08:00
default 1500
range 80 1500
slip: Add driver for host to qemu connectivity The SLIP driver is using UART pipe driver to communicate with host when Zephyr is running in Qemu. Currently this is only used by networking sub-system when testing the networking stack. Change-Id: I432b4136670766a7fc190f146057924c266f9bea Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-09 17:26:52 +08:00
help
This option sets the MTU for the SLIP connection.
The value is only used when fragmenting the network
data into net_buf's. The actual SLIP connection
does not use this value.
drivers: net: slip: Convert to use new logging Convert the driver to use the new logging system. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2018-07-10 20:36:36 +08:00
module=SLIP
module-dep=LOG
module-str=Log level for slip driver
module-help=Sets log level for slip driver.
source "subsys/net/Kconfig.template.log_config.net"
slip: Add driver for host to qemu connectivity The SLIP driver is using UART pipe driver to communicate with host when Zephyr is running in Qemu. Currently this is only used by networking sub-system when testing the networking stack. Change-Id: I432b4136670766a7fc190f146057924c266f9bea Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-09 17:26:52 +08:00
config SLIP_STATISTICS
bool "SLIP network connection statistics"
help
This option enables statistics support for SLIP driver.
slip: Support TAP functionality If CONFIG_SLIP_TAP is defined, then ethernet link layer header is added before the packet. Change-Id: I3d266017f85683999d3c67de49b75b60686d7ba7 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-24 16:19:53 +08:00
config SLIP_TAP
bool "Use TAP interface to host"
net: slip: Clarify slip settings in Kconfig As SLIP TAP is now the default after the commit ca0ad13a61ff5 ("net: enable SLIP only on QEMU targets"), clarify the comments and settings in various Kconfig files that talk about slip. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-07-27 19:09:11 +08:00
default y
net: Add an L2 layer Net core then does not know anything about l2 related logic. For instance ARP is used in ethernet l2 API and nowhere else. This will be helpful when adding different technologies altogether. Currently, only SLIP driver is enabled to use relevant l2 layer. Change-Id: I03c93326321028d04222733ca4083e3c6b785202 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2016-06-01 21:06:27 +08:00
select NET_L2_ETHERNET
slip: Support TAP functionality If CONFIG_SLIP_TAP is defined, then ethernet link layer header is added before the packet. Change-Id: I3d266017f85683999d3c67de49b75b60686d7ba7 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-24 16:19:53 +08:00
help
net: slip: Clarify slip settings in Kconfig As SLIP TAP is now the default after the commit ca0ad13a61ff5 ("net: enable SLIP only on QEMU targets"), clarify the comments and settings in various Kconfig files that talk about slip. Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2017-07-27 19:09:11 +08:00
In TAP the Ethernet frames are transferred over SLIP.
slip: Support TAP functionality If CONFIG_SLIP_TAP is defined, then ethernet link layer header is added before the packet. Change-Id: I3d266017f85683999d3c67de49b75b60686d7ba7 Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-24 16:19:53 +08:00
drivers: slip: Allow specifying the MAC address from config file The current state of affairs will not allow to set a MAC address and thus will initialize a random MAC address. However, when we are in a situation where we are trying to interface Zephyr OS QEMU VMs with physical targets for testing, this is not practical. We need to create a macvtap interface, on which we need to set the MAC address of the Zephyr OS SLIP device so packets can be routed. There is no way to guess which random address is going to be used, and there is no practical way to query it. So this patch adds a CONFIG_SLIP_MAC_ADDR config setting. slip_iface_init() is changed to take the code from slip_get_mac() for initializing the MAC address (which should be happening there anyway) and if CONFIG_SLIP_MAC_ADDR is set, it takes that one -- otherwise goes to generate a random one. Change-Id: I55a68f2743604f310d41c934783eca82084d7e94 Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
2017-03-10 14:32:50 +08:00
config SLIP_MAC_ADDR
string "MAC address for the interface"
help
Specify a MAC address for the SLIP interface in the form of
spell: fix Kconfig help typos: /boards /drivers Fix misspellings in Kconfig help text Change-Id: I3ae28a5d23d8e266612114bc0eb8a6e158129dc7 Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-04-22 01:29:51 +08:00
six hex 8-bit chars separated by colons (e.g.:
drivers: slip: Allow specifying the MAC address from config file The current state of affairs will not allow to set a MAC address and thus will initialize a random MAC address. However, when we are in a situation where we are trying to interface Zephyr OS QEMU VMs with physical targets for testing, this is not practical. We need to create a macvtap interface, on which we need to set the MAC address of the Zephyr OS SLIP device so packets can be routed. There is no way to guess which random address is going to be used, and there is no practical way to query it. So this patch adds a CONFIG_SLIP_MAC_ADDR config setting. slip_iface_init() is changed to take the code from slip_get_mac() for initializing the MAC address (which should be happening there anyway) and if CONFIG_SLIP_MAC_ADDR is set, it takes that one -- otherwise goes to generate a random one. Change-Id: I55a68f2743604f310d41c934783eca82084d7e94 Signed-off-by: Inaky Perez-Gonzalez <inaky.perez-gonzalez@intel.com>
2017-03-10 14:32:50 +08:00
aa:33:cc:22:e2:c0). The default is an empty string, which
means the code will make 00:00:5E:00:53:XX, where XX will be
random.
slip: Add driver for host to qemu connectivity The SLIP driver is using UART pipe driver to communicate with host when Zephyr is running in Qemu. Currently this is only used by networking sub-system when testing the networking stack. Change-Id: I432b4136670766a7fc190f146057924c266f9bea Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com>
2016-05-09 17:26:52 +08:00
endif
drivers: net: loopback: Network loopback interface driver Loopback is a networking interface which doesn't actually transfer any data via link layer externally, and instead just mirrors back (i.e. any packet send to the loopback interface will be received from it). This interface very useful for testing. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2017-10-20 20:00:39 +08:00
#
# Net loopback options
#
menuconfig NET_LOOPBACK
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
bool "Net loopback driver"
drivers: net: loopback: Network loopback interface driver Loopback is a networking interface which doesn't actually transfer any data via link layer externally, and instead just mirrors back (i.e. any packet send to the loopback interface will be received from it). This interface very useful for testing. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2017-10-20 20:00:39 +08:00
select NET_L2_DUMMY
if NET_LOOPBACK
config SYS_LOG_NET_LOOPBACK_LEVEL
Kconfig: Use a short, consistent style for prompts Consistently use config FOO bool/int/hex/string "Prompt text" instead of config FOO bool/int/hex/string prompt "Prompt text" (...and a bunch of other variations that e.g. swapped the order of the type and the 'prompt', or put other properties between them). The shorthand is fully equivalent to using 'prompt'. It saves lines and avoids tricking people into thinking there is some semantic difference. Most of the grunt work was done by a modified version of https://unix.stackexchange.com/questions/26284/ how-can-i-use-sed-to-replace-a-multi-line-string/26290#26290, but some of the rarer variations had to be converted manually. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-08-14 22:19:20 +08:00
int "Net loopback driver log level"
drivers: net: loopback: Network loopback interface driver Loopback is a networking interface which doesn't actually transfer any data via link layer externally, and instead just mirrors back (i.e. any packet send to the loopback interface will be received from it). This interface very useful for testing. Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2017-10-20 20:00:39 +08:00
depends on SYS_LOG && NET_LOOPBACK
default 0
range 0 4
help
Sets log level for the driver.
Levels are:
0 OFF, do not write
1 ERROR, only write SYS_LOG_ERR
2 WARNING, write SYS_LOG_WRN in addition to previous level
3 INFO, write SYS_LOG_INF in addition to previous levels
4 DEBUG, write SYS_LOG_DBG in addition to previous levels
endif