OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/net/zperf/prj_bt.conf

34 lines
749 B
Plaintext
Raw Normal View History

net: zperf: Add bluetooth support Change-Id: I56f2000cef929d5d0ddae0d67bc222d20db06480 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2017-01-19 22:26:09 +08:00
CONFIG_NETWORKING=y
CONFIG_NET_LOG=y
CONFIG_NET_IPV6=y
CONFIG_NET_UDP=y
CONFIG_NET_TCP=n
CONFIG_NET_STATISTICS=y
net: Renaming net nbuf API to net pkt API There have been long lasting confusion between net_buf and net_nbuf. While the first is actually a buffer, the second one is not. It's a network buffer descriptor. More precisely it provides meta data about a network packet, and holds the chain of buffer fragments made of net_buf. Thus renaming net_nbuf to net_pkt and all names around it as well (function, Kconfig option, ..). Though net_pkt if the new name, it still inherit its logic from net_buf. ' This patch is the first of a serie that will separate completely net_pkt from net_buf. Change-Id: Iecb32d2a0d8f4647692e5328e54b5c35454194cd Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-04-03 23:14:35 +08:00
CONFIG_NET_PKT_RX_COUNT=14
CONFIG_NET_PKT_TX_COUNT=14
CONFIG_NET_BUF_RX_COUNT=28
CONFIG_NET_BUF_TX_COUNT=28
CONFIG_NET_BUF_DATA_SIZE=512
net: zperf: Add bluetooth support Change-Id: I56f2000cef929d5d0ddae0d67bc222d20db06480 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2017-01-19 22:26:09 +08:00
CONFIG_NET_IF_UNICAST_IPV6_ADDR_COUNT=5
CONFIG_NET_IF_MCAST_IPV6_ADDR_COUNT=5
CONFIG_NET_IF_UNICAST_IPV4_ADDR_COUNT=1
CONFIG_NET_MAX_CONTEXTS=3
CONFIG_NET_CONTEXT_SYNC_RECV=y
CONFIG_INIT_STACKS=y
CONFIG_TEST_RANDOM_GENERATOR=y
CONFIG_SYS_LOG_SHOW_COLOR=y
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_NET_L2_BT=y
net: zperf: Add bluetooth support Change-Id: I56f2000cef929d5d0ddae0d67bc222d20db06480 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2017-01-19 22:26:09 +08:00
CONFIG_NET_SHELL=y
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_NET_L2_BT_SHELL=y
net: zperf: Add bluetooth support Change-Id: I56f2000cef929d5d0ddae0d67bc222d20db06480 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2017-01-19 22:26:09 +08:00
CONFIG_CONSOLE_HANDLER=y
CONFIG_CONSOLE_SHELL=y
CONFIG_PRINTK=y
net: Rename Kconfig.samples and its main option for future changes s/SAMPLES/APP for name shortening. Applying the change where relevant. Not only IP addresse will be available as samples settings there but also IEEE 802.15.4 channel, pan_id, and more for instance. Change-Id: I05dd24989bd0c804d9588092d67044a3e063bc88 Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
2017-03-15 23:01:47 +08:00
CONFIG_NET_APP_SETTINGS=y
CONFIG_NET_APP_MY_IPV6_ADDR="2001:db8::1"
CONFIG_NET_APP_PEER_IPV6_ADDR="2001:db8::2"