OrgApache/incubator-nuttx
OrgApache
/
incubator-nuttx
mirror of https://github.com/apache/incubator-nuttx.git
1
0
Fork 0
Code Issues Releases Wiki Activity
incubator-nuttx/net/Kconfig

375 lines
10 KiB
Plaintext
Raw Normal View History

Adding skeleton Kconfig files (part 1 of 2) git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4564 42af7a65-404d-4744-a932-0658087f49c3
2012-04-06 23:49:35 +08:00
#
# For a description of the syntax of this configuration file,
Fix references to the no-longer-existent misc/ directory in comments, README files, and documentation
2015-06-28 22:08:57 +08:00
# see the file kconfig-language.txt in the NuttX tools repository.
Adding skeleton Kconfig files (part 1 of 2) git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4564 42af7a65-404d-4744-a932-0658087f49c3
2012-04-06 23:49:35 +08:00
#
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
Add logic to enable DEBUG_NET if NET=n but WL_CC3000=y
2013-10-24 01:48:57 +08:00
config ARCH_HAVE_NET
bool
default n
config ARCH_HAVE_PHY
bool
default n
Kconfig: Move the ARCH_PHY_INTERRUPT option to net/Kconfig and make it unconditionally selectable.
2020-02-09 08:55:41 +08:00
config ARCH_PHY_INTERRUPT
bool
default n
net:Add ARCH_PHY_POLLED option
2020-09-18 20:04:49 +08:00
config ARCH_PHY_POLLED
bool
default n
Remove duplicated NET_SLIP option from drivers/net/Kconfig
2020-02-02 14:20:43 +08:00
config ARCH_HAVE_NETDEV_STATISTICS
bool
default n
This commit adds an as-of-yet untested implemented of UDP write buffering. Squashed commit of the following: net/udp: Address most of the issues with UDP write buffering. There is a remaining issue with handling one network going down in a multi-network environment. None of this has been test but it is certainly ready for test. Hence, the feature is marked EXPERIMENTAL. net/udp: Some baby steps toward a corrected write buffering design. net/udp: Remove pesky write buffer macros. Eliminate trailing space at the end of lines. net/udp: A little more UDP write buffering logic. Still at least on big gaping hole in the design. net/udp: Undefined CONFIG_NET_SENDTO_TIMEOUT. net/udp: Crude, naive port of the TCP write buffering logic into UDP. This commit is certainly non-functional and is simply a starting point for the implementatin of UDP write buffering. net/udp: Rename udp/udp_psock_sendto.c udp/udp_psock_sendto_unbuffered.c.
2018-01-23 08:32:02 +08:00
config NET_WRITE_BUFFERS
bool
default n
Make the read ahead buffer unselectable Here is the email loop talk about why it is better to remove the option: https://groups.google.com/forum/#!topic/nuttx/AaNkS7oU6R0 Change-Id: Ib66c037752149ad4b2787ef447f966c77aa12aad Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
2020-01-11 11:56:03 +08:00
select MM_IOB
This commit adds an as-of-yet untested implemented of UDP write buffering. Squashed commit of the following: net/udp: Address most of the issues with UDP write buffering. There is a remaining issue with handling one network going down in a multi-network environment. None of this has been test but it is certainly ready for test. Hence, the feature is marked EXPERIMENTAL. net/udp: Some baby steps toward a corrected write buffering design. net/udp: Remove pesky write buffer macros. Eliminate trailing space at the end of lines. net/udp: A little more UDP write buffering logic. Still at least on big gaping hole in the design. net/udp: Undefined CONFIG_NET_SENDTO_TIMEOUT. net/udp: Crude, naive port of the TCP write buffering logic into UDP. This commit is certainly non-functional and is simply a starting point for the implementatin of UDP write buffering. net/udp: Rename udp/udp_psock_sendto.c udp/udp_psock_sendto_unbuffered.c.
2018-01-23 08:32:02 +08:00
config NET_READAHEAD
bool
default n
Make the read ahead buffer unselectable Here is the email loop talk about why it is better to remove the option: https://groups.google.com/forum/#!topic/nuttx/AaNkS7oU6R0 Change-Id: Ib66c037752149ad4b2787ef447f966c77aa12aad Signed-off-by: Xiang Xiao <xiaoxiang@xiaomi.com>
2020-01-11 11:56:03 +08:00
select MM_IOB
This commit adds an as-of-yet untested implemented of UDP write buffering. Squashed commit of the following: net/udp: Address most of the issues with UDP write buffering. There is a remaining issue with handling one network going down in a multi-network environment. None of this has been test but it is certainly ready for test. Hence, the feature is marked EXPERIMENTAL. net/udp: Some baby steps toward a corrected write buffering design. net/udp: Remove pesky write buffer macros. Eliminate trailing space at the end of lines. net/udp: A little more UDP write buffering logic. Still at least on big gaping hole in the design. net/udp: Undefined CONFIG_NET_SENDTO_TIMEOUT. net/udp: Crude, naive port of the TCP write buffering logic into UDP. This commit is certainly non-functional and is simply a starting point for the implementatin of UDP write buffering. net/udp: Rename udp/udp_psock_sendto.c udp/udp_psock_sendto_unbuffered.c.
2018-01-23 08:32:02 +08:00
Add new configuratin CONFIG_NET_MCASTGROUP. This option is selected automatically if either CONFIG_NET_IGMP or CONFIG_NET_MLD are selected. Most conditional logic based on CONFIG_NET_IGMP replaced with conditioning on CONFIG_NET_MCASTGROUP.
2018-11-01 05:03:51 +08:00
config NET_MCASTGROUP
bool
default n
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
config NET
bool "Networking support"
default n
Add logic to enable DEBUG_NET if NET=n but WL_CC3000=y
2013-10-24 01:48:57 +08:00
select ARCH_HAVE_NET
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
---help---
Enable or disable all network features
if NET
Completes basic changes to support per-device/per-link TCP receive window size
2014-11-17 01:15:21 +08:00
config NET_PROMISCUOUS
bool "Promiscuous mode"
default n
---help---
Force the Ethernet driver to operate in promiscuous mode (if supported
by the Ethernet driver).
menu "Driver buffer configuration"
This commit attempts remove some long standard confusion in naming and some actual problems that result from the naming confusion. The basic problem is the standard MTU does not include the size of the Ethernet header. For clarity, I changed the naming of most things called MTU to PKTSIZE. For example, CONFIG_NET_ETH_MTU is now CONFIG_NET_ETH_PKTSIZE. This makes the user interface a little hostile. People thing of an MTU of 1500 bytes, but the corresponding packet is really 1514 bytes (including the 14 byte Ethernet header). A more friendly solution would configure the MTU (as before), but then derive the packet buffer size by adding the MAC header length. Instead, we define the packet buffer size then derive the MTU. The MTU is not common currency in networking. On the wire, the only real issue is the MSS which is derived from MTU by subtracting the IP header and TCP header sizes (for the case of TCP). Now it is derived for the PKTSIZE by subtracting the IP header, the TCP header, and the MAC header sizes. So we should be all good and without the recurring 14 byte error in MTU's and MSS's. Squashed commit of the following: Trivial update to fix some spacing issues. net/: Rename several macros containing _MTU to _PKTSIZE. net/: Rename CONFIG_NET_SLIP_MTU to CONFIG_NET_SLIP_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_6LOWPAN_MTU to CONFIG_NET_6LOWPAN_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_ETH_MTU to CONFIG_NET_ETH_PKTSIZE. This is not the MTU which does not include the size of the link layer header. This is the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename the file d_mtu in the network driver structure to d_pktsize. That value saved there is not the MTU. The packetsize is the memory large enough to hold the maximum packet PLUS the size of the link layer header. The MTU does not include the link layer header.
2018-07-05 04:10:40 +08:00
config NET_ETH_PKTSIZE
int "Ethernet packet buffer size"
Completes conversion of CONFIG_NET_BUFIZE to CONFIG_NET_ETH/SLIP_MTU
2014-11-16 23:22:38 +08:00
default 1294 if NET_IPv6
default 590 if !NET_IPv6
net/Kconfig: Ethernet packet buffer size cannot be permitted to go below 1294 is IPv6 is selected.
2019-08-31 23:08:32 +08:00
range 1294 1518 if NET_IPv6
range 590 1518 if !NET_IPv6
Completes conversion of CONFIG_NET_BUFIZE to CONFIG_NET_ETH/SLIP_MTU
2014-11-16 23:22:38 +08:00
depends on NET_ETHERNET
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
---help---
Add true and false commands; repartition some logic to better support forthcoming looping
2014-01-18 03:24:44 +08:00
Packet buffer size. This size includes the TCP/UDP payload plus the
Completes conversion of CONFIG_NET_BUFIZE to CONFIG_NET_ETH/SLIP_MTU
2014-11-16 23:22:38 +08:00
size of TCP/UDP header, the IP header, and the Ethernet header.
This commit attempts remove some long standard confusion in naming and some actual problems that result from the naming confusion. The basic problem is the standard MTU does not include the size of the Ethernet header. For clarity, I changed the naming of most things called MTU to PKTSIZE. For example, CONFIG_NET_ETH_MTU is now CONFIG_NET_ETH_PKTSIZE. This makes the user interface a little hostile. People thing of an MTU of 1500 bytes, but the corresponding packet is really 1514 bytes (including the 14 byte Ethernet header). A more friendly solution would configure the MTU (as before), but then derive the packet buffer size by adding the MAC header length. Instead, we define the packet buffer size then derive the MTU. The MTU is not common currency in networking. On the wire, the only real issue is the MSS which is derived from MTU by subtracting the IP header and TCP header sizes (for the case of TCP). Now it is derived for the PKTSIZE by subtracting the IP header, the TCP header, and the MAC header sizes. So we should be all good and without the recurring 14 byte error in MTU's and MSS's. Squashed commit of the following: Trivial update to fix some spacing issues. net/: Rename several macros containing _MTU to _PKTSIZE. net/: Rename CONFIG_NET_SLIP_MTU to CONFIG_NET_SLIP_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_6LOWPAN_MTU to CONFIG_NET_6LOWPAN_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_ETH_MTU to CONFIG_NET_ETH_PKTSIZE. This is not the MTU which does not include the size of the link layer header. This is the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename the file d_mtu in the network driver structure to d_pktsize. That value saved there is not the MTU. The packetsize is the memory large enough to hold the maximum packet PLUS the size of the link layer header. The MTU does not include the link layer header.
2018-07-05 04:10:40 +08:00
This value is related to the MTU (Maximum Transmission Unit), except
that it includes the size of the link layer header; the payload is
the MSS (Maximum Segment Size).
net/Kconfig: Improved default values and comments
2014-01-17 06:08:51 +08:00
IPv4 hosts are required to be able to handle an MSS of at least
536 octets, resulting in a minimum buffer size of 536+20+20+14 =
Completes conversion of CONFIG_NET_BUFIZE to CONFIG_NET_ETH/SLIP_MTU
2014-11-16 23:22:38 +08:00
590.
net/Kconfig: Improved default values and comments
2014-01-17 06:08:51 +08:00
IPv6 hosts are required to be able to handle an MSS of 1220 octets,
Fix typos in comments and documentation.
2020-03-17 03:42:34 +08:00
resulting in a minimum buffer size of 1220+20+40+14 = 1294
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
Update some help comments in two Kconfig files.
2018-07-05 05:36:31 +08:00
To get an MTU of 1500, for example, you would need packet buffer of
size 1514.
This commit attempts remove some long standard confusion in naming and some actual problems that result from the naming confusion. The basic problem is the standard MTU does not include the size of the Ethernet header. For clarity, I changed the naming of most things called MTU to PKTSIZE. For example, CONFIG_NET_ETH_MTU is now CONFIG_NET_ETH_PKTSIZE. This makes the user interface a little hostile. People thing of an MTU of 1500 bytes, but the corresponding packet is really 1514 bytes (including the 14 byte Ethernet header). A more friendly solution would configure the MTU (as before), but then derive the packet buffer size by adding the MAC header length. Instead, we define the packet buffer size then derive the MTU. The MTU is not common currency in networking. On the wire, the only real issue is the MSS which is derived from MTU by subtracting the IP header and TCP header sizes (for the case of TCP). Now it is derived for the PKTSIZE by subtracting the IP header, the TCP header, and the MAC header sizes. So we should be all good and without the recurring 14 byte error in MTU's and MSS's. Squashed commit of the following: Trivial update to fix some spacing issues. net/: Rename several macros containing _MTU to _PKTSIZE. net/: Rename CONFIG_NET_SLIP_MTU to CONFIG_NET_SLIP_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_6LOWPAN_MTU to CONFIG_NET_6LOWPAN_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_ETH_MTU to CONFIG_NET_ETH_PKTSIZE. This is not the MTU which does not include the size of the link layer header. This is the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename the file d_mtu in the network driver structure to d_pktsize. That value saved there is not the MTU. The packetsize is the memory large enough to hold the maximum packet PLUS the size of the link layer header. The MTU does not include the link layer header.
2018-07-05 04:10:40 +08:00
config NET_SLIP_PKTSIZE
net/Kconfig: Uncomment the prompt of NET_SLIP_PKTSIZE
2018-08-27 04:28:35 +08:00
int "SLIP packet buffer size"
Completes conversion of CONFIG_NET_BUFIZE to CONFIG_NET_ETH/SLIP_MTU
2014-11-16 23:22:38 +08:00
default 296
depends on NET_SLIP
range 296 1518
---help---
Networking: With these changes, I can ping the local loopback device from the simulator
2015-08-25 03:49:12 +08:00
Provides the size of the SLIP packet buffers. This size includes
the TCP/UDP payload plus the size of TCP/UDP header and the IP header.
This commit attempts remove some long standard confusion in naming and some actual problems that result from the naming confusion. The basic problem is the standard MTU does not include the size of the Ethernet header. For clarity, I changed the naming of most things called MTU to PKTSIZE. For example, CONFIG_NET_ETH_MTU is now CONFIG_NET_ETH_PKTSIZE. This makes the user interface a little hostile. People thing of an MTU of 1500 bytes, but the corresponding packet is really 1514 bytes (including the 14 byte Ethernet header). A more friendly solution would configure the MTU (as before), but then derive the packet buffer size by adding the MAC header length. Instead, we define the packet buffer size then derive the MTU. The MTU is not common currency in networking. On the wire, the only real issue is the MSS which is derived from MTU by subtracting the IP header and TCP header sizes (for the case of TCP). Now it is derived for the PKTSIZE by subtracting the IP header, the TCP header, and the MAC header sizes. So we should be all good and without the recurring 14 byte error in MTU's and MSS's. Squashed commit of the following: Trivial update to fix some spacing issues. net/: Rename several macros containing _MTU to _PKTSIZE. net/: Rename CONFIG_NET_SLIP_MTU to CONFIG_NET_SLIP_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_6LOWPAN_MTU to CONFIG_NET_6LOWPAN_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_ETH_MTU to CONFIG_NET_ETH_PKTSIZE. This is not the MTU which does not include the size of the link layer header. This is the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename the file d_mtu in the network driver structure to d_pktsize. That value saved there is not the MTU. The packetsize is the memory large enough to hold the maximum packet PLUS the size of the link layer header. The MTU does not include the link layer header.
2018-07-05 04:10:40 +08:00
This value is related to the MTU (Maximum Transmission Unit), except
that it includes the size of the link layer header; the payload is
Update some help comments in two Kconfig files.
2018-07-05 05:36:31 +08:00
the MSS (Maximum Segment Size). SLIP has no link layer header so for
SLIP the MTU is the same as the PKTSIZE.
Networking: With these changes, I can ping the local loopback device from the simulator
2015-08-25 03:49:12 +08:00
Trivial spelling corrections in comments; update some comments in a Kconfig file.
2018-06-25 05:01:49 +08:00
SLIP is required to support at least 256+20+20 = 296. Values other than
Networking: With these changes, I can ping the local loopback device from the simulator
2015-08-25 03:49:12 +08:00
296 are not recommended.
The Linux slip module hard-codes its MTU size to 296 (40 bytes for
Remove duplicated NET_SLIP option from drivers/net/Kconfig
2020-02-02 14:20:43 +08:00
the IP+TCP headers plus 256 bytes of data). So you might as well
This commit attempts remove some long standard confusion in naming and some actual problems that result from the naming confusion. The basic problem is the standard MTU does not include the size of the Ethernet header. For clarity, I changed the naming of most things called MTU to PKTSIZE. For example, CONFIG_NET_ETH_MTU is now CONFIG_NET_ETH_PKTSIZE. This makes the user interface a little hostile. People thing of an MTU of 1500 bytes, but the corresponding packet is really 1514 bytes (including the 14 byte Ethernet header). A more friendly solution would configure the MTU (as before), but then derive the packet buffer size by adding the MAC header length. Instead, we define the packet buffer size then derive the MTU. The MTU is not common currency in networking. On the wire, the only real issue is the MSS which is derived from MTU by subtracting the IP header and TCP header sizes (for the case of TCP). Now it is derived for the PKTSIZE by subtracting the IP header, the TCP header, and the MAC header sizes. So we should be all good and without the recurring 14 byte error in MTU's and MSS's. Squashed commit of the following: Trivial update to fix some spacing issues. net/: Rename several macros containing _MTU to _PKTSIZE. net/: Rename CONFIG_NET_SLIP_MTU to CONFIG_NET_SLIP_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_6LOWPAN_MTU to CONFIG_NET_6LOWPAN_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_ETH_MTU to CONFIG_NET_ETH_PKTSIZE. This is not the MTU which does not include the size of the link layer header. This is the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename the file d_mtu in the network driver structure to d_pktsize. That value saved there is not the MTU. The packetsize is the memory large enough to hold the maximum packet PLUS the size of the link layer header. The MTU does not include the link layer header.
2018-07-05 04:10:40 +08:00
set CONFIG_NET_SLIP_PKTSIZE to 296 as well.
Networking: With these changes, I can ping the local loopback device from the simulator
2015-08-25 03:49:12 +08:00
There may be an issue with this setting, however. I see that Linux
uses a MTU of 296 and window of 256, but actually only sends 168
bytes of data: 40 + 128. I believe that is to allow for the 2x
worst cast packet expansion. Ideally we would like to advertise the
256 MSS, but restrict transfers to 128 bytes (possibly by modifying
Networking: Get rid of the tcp_mss macro. It is confusing and only obfuscates what is really going on
2015-08-27 22:39:17 +08:00
the MSS value in the TCP connection structure).
Networking: With these changes, I can ping the local loopback device from the simulator
2015-08-25 03:49:12 +08:00
Add missing CONFIG_NET_GUARDSIZE to Kconfig
2014-06-19 22:18:46 +08:00
config NET_GUARDSIZE
int "Driver I/O guard size"
default 2
---help---
Network drivers often receive packets with garbage at the end and
are longer than the size of packet in the TCP header. The following
"fudge" factor increases the size of the I/O buffering by a small
amount to allocate slightly oversize packets. After receipt, the
packet size will be chopped down to the size indicated in the TCP
header.
changes for clean build with Ethernet+SLIP
2014-11-17 01:27:53 +08:00
endmenu # Driver buffer configuration
Completes basic changes to support per-device/per-link TCP receive window size
2014-11-17 01:15:21 +08:00
Squashed commit of the following: commit 5b7b6e6e616c475c782e9883ada9f4a3b7cb4e2c Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 11:13:17 2017 -0600 IEEE 802.15.4 network device: Make same changes as per loopback device so that it will build with PF_IEEE802154 but without 6LoWPAN. commit d656a98cf8eab2f20e884224b52cd47ec35df4cc Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 10:31:28 2017 -0600 PF_IEEE802154: More fixes to device registration and to IEEE 802.15.4 loopback driver for PF_IEEE802154 without 6LoWPAN. commit 866bb9cbb0c5af79734bbd434c07fa2560b6608f Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:58:13 2017 -0600 Network: Reorganize some Kconfig selections. commit 230b4cb48008cba5fccdafa22340df1d43584829 Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:19:53 2017 -0600 Changes to conditional compilation so that PF_IEEE802154 can build without 6LoWPAN commit d96cbd6520d40590a740f695c4cd72208ce872da Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:17:02 2017 -0600 configs/sim/pf_ieee802154: Disable 6LoWPAN, IPv6, TCP, and UDP. Now things do not build
2017-08-21 01:14:43 +08:00
menu "Link layer support"
Netwoek: Ada a parameter to netdev_register() to indicate the link protocol supported by the driver. Use this value to replace some logic commited yesterday
2014-11-15 22:22:51 +08:00
Add CONFIG_NET_ETHERNET (not used yet)
2014-06-01 23:40:23 +08:00
config NET_ETHERNET
Network: Misc fixes for clean complete with both Ethernet and SLIP enabled
2014-11-15 22:55:50 +08:00
bool "Ethernet support"
net/: Permit net/neighbor to build when IPv6 is defined, but not Ethernet. Needs more work to support 6loWPAN. Also included, some minor configuration updates for 6loWPAN.
2017-04-01 01:15:16 +08:00
default y
Add CONFIG_NET_ETHERNET (not used yet)
2014-06-01 23:40:23 +08:00
---help---
If NET_SLIP is not selected, then Ethernet will be used (there is
no need to define anything special in the configuration file to use
Ethernet -- it is the default).
Networking: With these changes, I can ping the local loopback device from the simulator
2015-08-25 03:49:12 +08:00
config NET_LOOPBACK
bool "Local loopback"
Remove NETDEV_LOOPBACK option, NET_LOOPBACK is enough
2020-02-02 14:15:24 +08:00
select ARCH_HAVE_NETDEV_STATISTICS
Networking: With these changes, I can ping the local loopback device from the simulator
2015-08-25 03:49:12 +08:00
default n
---help---
Eliminate CONFIG_NO_NOINTS. Lots of files changed -> lots of testing needed.
2016-12-04 06:28:19 +08:00
Add support for the local network loopback device, lo.
Networking: With these changes, I can ping the local loopback device from the simulator
2015-08-25 03:49:12 +08:00
Network Loopback Driver: A configuration option to control packet size. Historically, the loopback driver used the largest packet size of all enabled link layer protocols. This permitted packets to be forward via the loopbak device with no major loss of performance. However, in experimenting with configurations where no other link layer protocols were enabled, this means the loopback packet size was set to the smallest possible size, to the SLIP minimum of 296 bytes. This resulted in terrible loopback performance. This commit adds an option to increase the loopback packet size with the option CONFIG_NET_LOOPBACK_PACKETSIZE. The loopback driver packet buffer should be quite large. The larger the loopback packet buffer, the better will be TCP performance of the loopback transfers. The Linux loopback device historically used packet buffers of size 16Kb, but that was increased in recent Linux versions to 64Kb. Those sizes may be excessive for resource constrained MCUs, however. The network still enforces the lower limit that is the maximum packet size of all enabled link layer protocols. But this new option permits the loopback packet size to be increased from that. * net/Kconfig: Adds CONFIG_NET_LOOPBACK_PKTSIZE option * include/nuttx/net/netconfig.h: Assures that the packet size that is used is at least as large as the largest packet size of other link layer protocols. * drivers/net/loopback.c: Use that larger packet size. * boards/sim/sim/sim/configs/tcploop/defconfig: Set the loopback packet size to 1500
2020-02-11 08:35:02 +08:00
config NET_LOOPBACK_PKTSIZE
int "Loopback packet buffer size"
default 0
depends on NET_LOOPBACK
range 0 65535
---help---
The loopback driver packet buffer should be quite large. The larger
the loopback packet buffer, the better will be TCP performance of
the loopback transfers. The Linux loopback device historically used
packet buffers of size 16Kb, but that was increased in recent Linux
versions to 64Kb. Those sizes may be excessive for resource
constrained MCUs, however.
The network enforces a lower limit that is the maximum packet size
of all enabled link layer protocols. The default value of
CONFIG_NET_LOOPBACK_PKTSIZE is zero, meaning that this maximum
packet size will be used by loopback driver.
Fix issues reported on PR #1233
2020-06-15 06:59:38 +08:00
menuconfig NET_MBIM
Fix wrong space instead of TAB
2020-06-15 08:08:20 +08:00
bool "MBIM modem support"
Fix issues reported on PR #1233
2020-06-15 06:59:38 +08:00
depends on USBHOST_CDCMBIM
default n
Squashed commit of the following: commit 5b7b6e6e616c475c782e9883ada9f4a3b7cb4e2c Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 11:13:17 2017 -0600 IEEE 802.15.4 network device: Make same changes as per loopback device so that it will build with PF_IEEE802154 but without 6LoWPAN. commit d656a98cf8eab2f20e884224b52cd47ec35df4cc Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 10:31:28 2017 -0600 PF_IEEE802154: More fixes to device registration and to IEEE 802.15.4 loopback driver for PF_IEEE802154 without 6LoWPAN. commit 866bb9cbb0c5af79734bbd434c07fa2560b6608f Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:58:13 2017 -0600 Network: Reorganize some Kconfig selections. commit 230b4cb48008cba5fccdafa22340df1d43584829 Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:19:53 2017 -0600 Changes to conditional compilation so that PF_IEEE802154 can build without 6LoWPAN commit d96cbd6520d40590a740f695c4cd72208ce872da Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:17:02 2017 -0600 configs/sim/pf_ieee802154: Disable 6LoWPAN, IPv6, TCP, and UDP. Now things do not build
2017-08-21 01:14:43 +08:00
menuconfig NET_SLIP
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
bool "SLIP support"
Remove duplicated NET_SLIP option from drivers/net/Kconfig
2020-02-02 14:20:43 +08:00
select ARCH_HAVE_NETDEV_STATISTICS
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
default n
---help---
Enables building of the SLIP driver. SLIP requires
Eliminate CONFIG_NO_NOINTS. Lots of files changed -> lots of testing needed.
2016-12-04 06:28:19 +08:00
at least one IP protocol selected.
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
SLIP supports point-to-point IP communications over a serial port.
networking: Update some comments to correct the naming used for the link layer.
2018-10-20 20:35:39 +08:00
The default link layer for network layer is Ethernet. If NET_SLIP
is defined in the NuttX configuration file, then SLIP will be
supported. The basic differences between the SLIP and Ethernet
include/nuttx/net/netdev.h and several Ethernet drivers in arch/: Most network drivers to not support statistics. Those that do only support them when DEBUG is enabled. Each driver collects an architecture specific set of statistics and there is no mechanism in place to view those statistics. Thus, the driver feature was mostly useless. This change standardizes the driver statistics and puts the definition in the common network device structure defined in netdev.h where they can be accessed by network applications. All Ethernet drivers that collect statistics have been adapted to use these common statistics.
2015-11-27 02:08:09 +08:00
configurations is that when SLIP is selected:
net/Kconfig: Improved default values and comments
2014-01-17 06:08:51 +08:00
* The link level header (that comes before the IP header) is omitted.
* All MAC address processing is suppressed.
* ARP is disabled.
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
If NET_SLIP is not selected, then Ethernet will be used (there is
no need to define anything special in the configuration file to use
Partial implementation of driver-based UDP backlog still missing some logic. From Max Holtzberg.
2013-09-06 23:18:07 +08:00
Ethernet -- it is the default).
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
if NET_SLIP
Partial implementation of driver-based UDP backlog still missing some logic. From Max Holtzberg.
2013-09-06 23:18:07 +08:00
config SLIP_NINTERFACES
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
int "Number of SLIP interfaces"
default 1
---help---
Selects the number of physical SLIP
Partial implementation of driver-based UDP backlog still missing some logic. From Max Holtzberg.
2013-09-06 23:18:07 +08:00
interfaces to support.
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
Default: 1
config SLIP_STACKSIZE
int "SLIP stack size"
Introduce CONFIG_DEFAULT_TASK_STACKSIZE * The appropriate size of stack varies among archs. E.g. for 64-bit sim, 2048 is way too small, especially when the task happens to use host OS functionalities. I plan to allow an arch provide its own default. * I plan to use this to replace hardcoded "STACKSIZE = 2048" in APPDIR.
2020-03-27 09:51:03 +08:00
default DEFAULT_TASK_STACKSIZE
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
---help---
Introduce CONFIG_DEFAULT_TASK_STACKSIZE * The appropriate size of stack varies among archs. E.g. for 64-bit sim, 2048 is way too small, especially when the task happens to use host OS functionalities. I plan to allow an arch provide its own default. * I plan to use this to replace hardcoded "STACKSIZE = 2048" in APPDIR.
2020-03-27 09:51:03 +08:00
Select the stack size of the SLIP RX and TX tasks.
Add tools/cmpconfig.c to compare to configuration files git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@4592 42af7a65-404d-4744-a932-0658087f49c3
2012-04-12 07:06:30 +08:00
config SLIP_DEFPRIO
int "SLIP priority"
default 128
---help---
The priority of the SLIP RX and TX tasks. Default: 128
net/Kconfig: Improved default values and comments
2014-01-17 06:08:51 +08:00
endif # NET_SLIP
Add TUN device. From Max Neklyudov
2015-03-11 20:52:56 +08:00
Squashed commit of the following: commit 5b7b6e6e616c475c782e9883ada9f4a3b7cb4e2c Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 11:13:17 2017 -0600 IEEE 802.15.4 network device: Make same changes as per loopback device so that it will build with PF_IEEE802154 but without 6LoWPAN. commit d656a98cf8eab2f20e884224b52cd47ec35df4cc Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 10:31:28 2017 -0600 PF_IEEE802154: More fixes to device registration and to IEEE 802.15.4 loopback driver for PF_IEEE802154 without 6LoWPAN. commit 866bb9cbb0c5af79734bbd434c07fa2560b6608f Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:58:13 2017 -0600 Network: Reorganize some Kconfig selections. commit 230b4cb48008cba5fccdafa22340df1d43584829 Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:19:53 2017 -0600 Changes to conditional compilation so that PF_IEEE802154 can build without 6LoWPAN commit d96cbd6520d40590a740f695c4cd72208ce872da Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:17:02 2017 -0600 configs/sim/pf_ieee802154: Disable 6LoWPAN, IPv6, TCP, and UDP. Now things do not build
2017-08-21 01:14:43 +08:00
menuconfig NET_TUN
Add TUN device. From Max Neklyudov
2015-03-11 20:52:56 +08:00
bool "TUN Virtual Network Device support"
default n
include/nuttx/net/netdev.h and several Ethernet drivers in arch/: Most network drivers to not support statistics. Those that do only support them when DEBUG is enabled. Each driver collects an architecture specific set of statistics and there is no mechanism in place to view those statistics. Thus, the driver feature was mostly useless. This change standardizes the driver statistics and puts the definition in the common network device structure defined in netdev.h where they can be accessed by network applications. All Ethernet drivers that collect statistics have been adapted to use these common statistics.
2015-11-27 02:08:09 +08:00
select ARCH_HAVE_NETDEV_STATISTICS
Add TUN device. From Max Neklyudov
2015-03-11 20:52:56 +08:00
if NET_TUN
config TUN_NINTERFACES
int "Number of TUN interfaces"
default 1
range 1 8
---help---
Selects the number of TUN
interfaces to support.
Default: 1
This commit attempts remove some long standard confusion in naming and some actual problems that result from the naming confusion. The basic problem is the standard MTU does not include the size of the Ethernet header. For clarity, I changed the naming of most things called MTU to PKTSIZE. For example, CONFIG_NET_ETH_MTU is now CONFIG_NET_ETH_PKTSIZE. This makes the user interface a little hostile. People thing of an MTU of 1500 bytes, but the corresponding packet is really 1514 bytes (including the 14 byte Ethernet header). A more friendly solution would configure the MTU (as before), but then derive the packet buffer size by adding the MAC header length. Instead, we define the packet buffer size then derive the MTU. The MTU is not common currency in networking. On the wire, the only real issue is the MSS which is derived from MTU by subtracting the IP header and TCP header sizes (for the case of TCP). Now it is derived for the PKTSIZE by subtracting the IP header, the TCP header, and the MAC header sizes. So we should be all good and without the recurring 14 byte error in MTU's and MSS's. Squashed commit of the following: Trivial update to fix some spacing issues. net/: Rename several macros containing _MTU to _PKTSIZE. net/: Rename CONFIG_NET_SLIP_MTU to CONFIG_NET_SLIP_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_6LOWPAN_MTU to CONFIG_NET_6LOWPAN_PKTSIZE and similarly for CONFIG_NET_TUN_MTU. These are not the MTU which does not include the size of the link layer header. These are the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename CONFIG_NET_ETH_MTU to CONFIG_NET_ETH_PKTSIZE. This is not the MTU which does not include the size of the link layer header. This is the full size of the packet buffer memory (minus any GUARD bytes). net/: Rename the file d_mtu in the network driver structure to d_pktsize. That value saved there is not the MTU. The packetsize is the memory large enough to hold the maximum packet PLUS the size of the link layer header. The MTU does not include the link layer header.
2018-07-05 04:10:40 +08:00
config NET_TUN_PKTSIZE
int "TUN packet buffer size"
drivers/net: Add option to use low-priority work queue to all drivers in drivers/net. Not yet added to all architecture-specific network drivers.
2016-11-18 23:22:49 +08:00
default 296
range 296 1518
Update some help comments in two Kconfig files.
2018-07-05 05:36:31 +08:00
---help---
Provides the size of the TUN packet buffers. This size includes
the TCP/UDP payload plus the size of TCP/UDP header and the IP header.
This value is related to the MTU (Maximum Transmission Unit), except
that it includes the size of the link layer header; the payload is
the MSS (Maximum Segment Size). TUN has no link layer header so for
TUN the MTU is the same as the PKTSIZE.
drivers/net: Add option to use low-priority work queue to all drivers in drivers/net. Not yet added to all architecture-specific network drivers.
2016-11-18 23:22:49 +08:00
Add TUN device. From Max Neklyudov
2015-03-11 20:52:56 +08:00
endif # NET_TUN
Move NETDEV_LATEINIT from drivers/net/Kconfig to net/Kconfig so that we can select NETDEV_LATEINIT without enabling NETDEVICES since the net driver in arch folder may need to initialize later too.
2018-11-12 20:36:26 +08:00
config NETDEV_LATEINIT
bool "Late driver initialization"
default n
---help---
Normally, networking initialization occur in the later phase of the
boot process in the function up_initialize() when it calls the
Fix typos.
2019-08-05 04:50:28 +08:00
driver initialization function, up_netinitialize(). This
Move NETDEV_LATEINIT from drivers/net/Kconfig to net/Kconfig so that we can select NETDEV_LATEINIT without enabling NETDEVICES since the net driver in arch folder may need to initialize later too.
2018-11-12 20:36:26 +08:00
initialization occurs after a sufficient about of the OS has been
initialized so that driver registration can be performed, but
before the completion of OS initialization and before the first
application is started.
In a few situations, however, you may want to suppress this early
network driver initialization. As examples:
- If you are using SLIP or PPPD, then there will be no network
driver to be initialized,
- Certain multi-network configurations where a simple call to
up_netinitialize() may be insufficient, and
- Situations where there are other board-level hardware
dependencies so that the hardware is not in an appropriate
state for up_netinitialize() to be called.
Examples of this latter situation includes such things as network
drivers that required some setup via an I2C I/O expander, or network
drivers that depend on USB, SPI, I2C, PCI, serial, or other
Fix a typo in kconfig text
2020-03-12 14:04:42 +08:00
interfaces that may not be ready when up_netinitialize() is normally
Move NETDEV_LATEINIT from drivers/net/Kconfig to net/Kconfig so that we can select NETDEV_LATEINIT without enabling NETDEVICES since the net driver in arch folder may need to initialize later too.
2018-11-12 20:36:26 +08:00
called.
networking: Update some comments to correct the naming used for the link layer.
2018-10-20 20:35:39 +08:00
endmenu # Link layer support
Network: Misc fixes for clean complete with both Ethernet and SLIP enabled
2014-11-15 22:55:50 +08:00
source "net/netdev/Kconfig"
Network: Add an IPv4 configuration option. Hardcoded to =y for now, but I would like to be able to select IPv4 and/or IPv6 in the future
2015-01-15 00:51:09 +08:00
Networking: Some fixes for compilation when both IPv4 and IPv6 are enabled
2015-01-18 23:23:22 +08:00
menu "Internet Protocol Selection"
Network: Add an IPv4 configuration option. Hardcoded to =y for now, but I would like to be able to select IPv4 and/or IPv6 in the future
2015-01-15 00:51:09 +08:00
config NET_IPv4
Networking: Some fixes for compilation when both IPv4 and IPv6 are enabled
2015-01-18 23:23:22 +08:00
bool "IPv4"
default y
Networking: Move net/ipv6 to net/neighbor
2015-01-17 06:49:48 +08:00
---help---
Build in support for IPv4.
Squashed commit of the following: commit 5b7b6e6e616c475c782e9883ada9f4a3b7cb4e2c Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 11:13:17 2017 -0600 IEEE 802.15.4 network device: Make same changes as per loopback device so that it will build with PF_IEEE802154 but without 6LoWPAN. commit d656a98cf8eab2f20e884224b52cd47ec35df4cc Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 10:31:28 2017 -0600 PF_IEEE802154: More fixes to device registration and to IEEE 802.15.4 loopback driver for PF_IEEE802154 without 6LoWPAN. commit 866bb9cbb0c5af79734bbd434c07fa2560b6608f Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:58:13 2017 -0600 Network: Reorganize some Kconfig selections. commit 230b4cb48008cba5fccdafa22340df1d43584829 Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:19:53 2017 -0600 Changes to conditional compilation so that PF_IEEE802154 can build without 6LoWPAN commit d96cbd6520d40590a740f695c4cd72208ce872da Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:17:02 2017 -0600 configs/sim/pf_ieee802154: Disable 6LoWPAN, IPv6, TCP, and UDP. Now things do not build
2017-08-21 01:14:43 +08:00
config NET_IPv6
Networking: Move net/ipv6 to net/neighbor
2015-01-17 06:49:48 +08:00
bool "IPv6"
default n
---help---
Networking: Some fixes for compilation when both IPv4 and IPv6 are enabled
2015-01-18 23:23:22 +08:00
Build in support for IPv6.
Network: Add an IPv4 configuration option. Hardcoded to =y for now, but I would like to be able to select IPv4 and/or IPv6 in the future
2015-01-15 00:51:09 +08:00
Networking: Move net/ipv6 to net/neighbor
2015-01-17 06:49:48 +08:00
source "net/neighbor/Kconfig"
Squashed commit of the following: commit 5b7b6e6e616c475c782e9883ada9f4a3b7cb4e2c Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 11:13:17 2017 -0600 IEEE 802.15.4 network device: Make same changes as per loopback device so that it will build with PF_IEEE802154 but without 6LoWPAN. commit d656a98cf8eab2f20e884224b52cd47ec35df4cc Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 10:31:28 2017 -0600 PF_IEEE802154: More fixes to device registration and to IEEE 802.15.4 loopback driver for PF_IEEE802154 without 6LoWPAN. commit 866bb9cbb0c5af79734bbd434c07fa2560b6608f Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:58:13 2017 -0600 Network: Reorganize some Kconfig selections. commit 230b4cb48008cba5fccdafa22340df1d43584829 Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:19:53 2017 -0600 Changes to conditional compilation so that PF_IEEE802154 can build without 6LoWPAN commit d96cbd6520d40590a740f695c4cd72208ce872da Author: Gregory Nutt <gnutt@nuttx.org> Date: Sun Aug 20 09:17:02 2017 -0600 configs/sim/pf_ieee802154: Disable 6LoWPAN, IPv6, TCP, and UDP. Now things do not build
2017-08-21 01:14:43 +08:00
menuconfig NET_6LOWPAN
bool "6LoWPAN support"
default n
select NETDEV_IOCTL
select NET_HAVE_STAR
depends on NET_IPv6
---help---
Enable support for Low power Wireless Personal Area Networking (6LoWPAN)
for IEEE 802.15.4 or other packet radios.
6loWPAN: Rename net/6lowpan to net/sixlowpan; Add Contike sixlowpan.h to include/nuttx/net
2017-03-28 04:53:52 +08:00
source "net/sixlowpan/Kconfig"
IP forwarding: Move to separate directory. A few fixes from early testing; In TUN driver, do all polling on worker thread. Otherwise, the stack gets very deep.
2017-07-08 08:33:06 +08:00
source "net/ipforward/Kconfig"
IP forwarding. Adds a little more structure to handle passing packets received on one network device to another network device. Logic is still incomplete.
2017-07-05 00:19:52 +08:00
Clicker2-STM32 + net/: Add configurations to support the endpoint and hub roles in a star topology. Fix various things that broke when IPv6 forwarding was enabled.
2017-06-29 22:16:46 +08:00
endmenu # Internet Protocol Selection
source "net/socket/Kconfig"
Networking: Move INET socket interface out of net/sockets to its own directory net/inet
2017-08-07 04:48:19 +08:00
source "net/inet/Kconfig"
Clicker2-STM32 + net/: Add configurations to support the endpoint and hub roles in a star topology. Fix various things that broke when IPv6 forwarding was enabled.
2017-06-29 22:16:46 +08:00
source "net/pkt/Kconfig"
source "net/local/Kconfig"
net/socket_rpmsg: add net socket rpmsg support Change-Id: Ie23ee4c0052cf2fc66972ea9bc5f11c070fbcf8a Signed-off-by: chao.an <anchao@xiaomi.com>
2020-11-05 20:30:49 +08:00
source "net/rpmsg/Kconfig"
net: Add SocketCAN support
2020-06-15 16:23:25 +08:00
source "net/can/Kconfig"
This commit brings in a fragmentary, experimental implementation of NETLINK sockets. There is not too much to that socket support on this initial commit, just the netlink socketer framework. However, I decided to bring it into master because there is a enough that I would not want to lose what is in place. And since it is dependent on CONFIG_EXPERIMENATL, its presence on master should be innocuous. Squashed commit of the following: net/netlink: Mark netlink support as EXPERIMENTAL. net/netlink/netlink_sockif.c: Add netlink_getpeername to the socket interface. net: Add getpeeername() support for netlink sockets. include/netpacket/netlink.h: Add a few more definitions and structures used at the NetLink interface. Still missing many. net/netlink: Add basic framework for Netlink socket support. include/: Add basic Netlink definitions.
2018-08-04 03:22:36 +08:00
source "net/netlink/Kconfig"
Clicker2-STM32 + net/: Add configurations to support the endpoint and hub roles in a star topology. Fix various things that broke when IPv6 forwarding was enabled.
2017-06-29 22:16:46 +08:00
source "net/tcp/Kconfig"
source "net/udp/Kconfig"
This comment adds (1) basic support for AF_BLUETOOTH sockets. The logic compiles but is still incomplete. Support for Bluetooth is general is still dependent on CONFIG_EXPERMIMENTAL because it is not yet ready for used. Squashed commit of the following: wireless/bluetooth: Some small changes that gets to a clean compile by just eliminating some incorrect implementations (still with a lot of warnings. The logic is still incomplete but now not so lethal. wireless/bluetooth: Restructuring: Connection interfaces should internal to wireless/bluetooth. include/nuttx/wireless/bt_conn.h removed and merged with wireless/bluetooth/bt_conn.h. Several fix to get closer to bt_netdev.c compiling. Need to design some not interfaces and use some existing interfaces to send and receiv packets. wireless/bluetooth: Some organization with some network device compile errors fixed. Still not even close to compiling. net/bluetooth: Fix numerous compile issues; Still open design issues with regard to the interface with the Bluetooth stack. wireless/bluetooth: Create bt_netdev.c with a crude copy of mac802154_netdev.c. Does not not even compile yet. include/nuttx/net: Add bluetooth.h. Content is not yet correct. net/netpackets: Add bluetooth.h. Update net/bluetooth to use new socket address definition. net/bluetooth: Some fixes for initial build. net/bluetooth: Add initial support for Bluetooth sockets. The initial cut is just the a clone of the IEEE 802.15.4 socket support with name changes. net/ieee802154: Fix some typos noted when cloning to create net/bluetooth.
2018-04-01 04:55:03 +08:00
source "net/bluetooth/Kconfig"
Squashed commit of the following: commit 2a3ab1652a2c95bcfc8be8380fc7cbdcb6472938 Author: Gregory Nutt <gnutt@nuttx.org> Date: Sat Aug 19 08:44:31 2017 -0600 PF_IEEE802154: Finish some missing bind() logic. Add configs/sim configuration for testing. commit 59be4b846a6e3bfe82087a888e3fdac9c3c414e5 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 19:30:04 2017 -0600 PF_IEEE802154: More renaming to decouple 6LoPAN from radios in general. commit 69fabb1aea76e54381bdc13de28a3f1441fb42f4 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 19:21:11 2017 -0600 PF_IEEE802154: Missed a few renamings. commit ff0af1bb25567720934cc1c2a721ccd92cc35f89 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 17:46:58 2017 -0600 PF_IEEE802154: A few bugfixes commit 01c7c84afd00cf907d280d30cfaf0fb2cf90e02e Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 17:01:31 2017 -0600 PF_IEEE802154: A few bugfixes commit dcef4056d1c1488c93151135f3b7106977faa903 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 16:31:05 2017 -0600 PF_IEEE802154: Bring in framework for sendto/recvfrom. Currently just a crude port of functions from net/pkt and do not provide the implemenation needed. commit 68c5b7b6dd3ab7eb2d0c19890abb38e6561b140e Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 15:18:31 2017 -0600 Trivial fix to typo in comment commit fd0af534c089569ccdbd59f13b85453de0a653ad Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 15:07:20 2017 -0600 PF_IEEE802154: Add device lookup logic; Rename some things that used to be used only by 6LoWPAN but now must be shared with PF_IEEE802154 and need more generic naming. commit 4fc80a1659f1c699b050775cefc7f6b631b46114 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 13:49:54 2017 -0600 PF_IEEE802154: Add driver poll logic. commit d83f71992df8764faa93f9425f1a7602a758f730 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 13:28:59 2017 -0600 PF_IEEE802154: Add frame input function. commit 77561b8c4d5d7be1f8d8eb62cf1a07229afe2048 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 12:46:29 2017 -0600 PF_IEEE802154: Socket type should be SOCK_DGRAM. Hook in socket interface. commit c0f90350282e9905d7f26a1b30f04cc6d6794648 Merge: 8b518abfd0 169c55e546 Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 09:36:32 2017 -0600 Merge remote-tracking branch 'origin/master' into pf_ieee802154 commit 8b518abfd07d492f5148f2c5fdf65604de9822da Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 09:35:39 2017 -0600 PF_IEEE802154: Add initialization and connection management logic. commit 98b62620b3cb420041d8ad14204f9410a8aace8c Author: Gregory Nutt <gnutt@nuttx.org> Date: Fri Aug 18 07:52:51 2017 -0600 PF_IEEE802154: Add basic build support and socket interface framework.
2017-08-19 22:48:52 +08:00
source "net/ieee802154/Kconfig"
Clicker2-STM32 + net/: Add configurations to support the endpoint and hub roles in a star topology. Fix various things that broke when IPv6 forwarding was enabled.
2017-06-29 22:16:46 +08:00
source "net/icmp/Kconfig"
source "net/icmpv6/Kconfig"
net/mld: Add basic build structure for Multicast Listener Discovery (MLD). No real MLD logic yet. Only a few hooks to capture and dispatch MLD ICMPv6 packets.
2018-11-01 04:10:19 +08:00
source "net/mld/Kconfig"
Clicker2-STM32 + net/: Add configurations to support the endpoint and hub roles in a star topology. Fix various things that broke when IPv6 forwarding was enabled.
2017-06-29 22:16:46 +08:00
source "net/igmp/Kconfig"
source "net/arp/Kconfig"
source "net/procfs/Kconfig"
source "net/usrsock/Kconfig"
source "net/utils/Kconfig"
config NET_STATISTICS
bool "Collect network statistics"
default n
---help---
Network layer statistics on or off
config NET_HAVE_STAR
bool
default n
---help---
Automatically enabled if at least one selected L2 protocol supports
a STAR topology. In order to support the star topology, the L2
protocol must support relaying all packets to a well-known hub node.
menu "Network Topologies"
6LoWPAN: Add configurable support for 6LoWPAN star topology. With this change, the endpoints which are the 'points' of the star will forward all traffic to the coordinator. The coordinator is assumed to be the 'hub' of the star. This function also implements IPv6 forwarding. That forwarding implementation is minimal, just enough to support the forwarding requirements of the star hub node.
2017-06-29 05:39:21 +08:00
config NET_STAR
bool "Enable star topology"
default n
depends on NET_HAVE_STAR && NET_IPv6
---help---
Enable support for a star network topology.
NOTE: Currently only supported by 6LoWPAN.
NOTE: L2 forwarding only supported for IPv6.
choice
prompt "Node role"
Clicker2-STM32 + net/: Add configurations to support the endpoint and hub roles in a star topology. Fix various things that broke when IPv6 forwarding was enabled.
2017-06-29 22:16:46 +08:00
depends on NET_STAR
default NET_STARPOINT
6LoWPAN: Add configurable support for 6LoWPAN star topology. With this change, the endpoints which are the 'points' of the star will forward all traffic to the coordinator. The coordinator is assumed to be the 'hub' of the star. This function also implements IPv6 forwarding. That forwarding implementation is minimal, just enough to support the forwarding requirements of the star hub node.
2017-06-29 05:39:21 +08:00
---help---
Specifies the role of this not in the star configuration.
config NET_STARPOINT
bool "Point node in star"
---help---
The node is a "point" in the star configuration and must send all
packets to the star hub node.
config NET_STARHUB
bool "Hub node of star"
select NET_IPFORWARD
---help---
This is the "hub" node in the star configurations. It will receive
packets packets from all "point" nodes and perform L2 forwarding of
the packets that are not destined for this node.
endchoice # Node role
Clicker2-STM32 + net/: Add configurations to support the endpoint and hub roles in a star topology. Fix various things that broke when IPv6 forwarding was enabled.
2017-06-29 22:16:46 +08:00
endmenu # Network Topologies
Network: Misc fixes for clean complete with both Ethernet and SLIP enabled
2014-11-15 22:55:50 +08:00
source "net/route/Kconfig"
net/Kconfig: Improved default values and comments
2014-01-17 06:08:51 +08:00
endif # NET