/Zephyr-latest/samples/bluetooth/mtu_update/ |
D | README.rst | 2 :name: MTU Update 5 Configure and exchange MTU between two devices. 10 Question: What do I have to do to update my ATT MTU? 12 | Answer: To get an ATT MTU of x octets, do the following: 25 Answer: Yes. [#mtu_exchange]_ The Bluetooth specification mandates a symmetric MTU for ATT. 30 This sample demonstrates the exchange of MTU between two devices to allow a 32 Updating the MTU can be useful to send bigger packets and so have a better 36 update their MTU. The MTU is not a negotiated value, the client and the server 37 will exchange their MTUs and choose the minimum of the two. Thus the two MTU can 38 be set to a different value, but the MTU of the server must be greater or equal [all …]
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | smp_transport.rst | 51 SMP protocol over serial is fragmented into MTU size frames; each 65 MTU - 3, is able to actually carry N = (MTU - 3) / 4 * 3 bytes 89 | | MTU - 3 bytes | | 111 | | MTU - 5 | | 135 | | MTU - 7 | | 154 | | MTU - 3 bytes | | 169 | | MTU - 3 | | 182 | | MTU - 5 | |
|
/Zephyr-latest/drivers/hdlc_rcp_if/ |
D | hdlc_rcp_if_nxp.c | 110 #define MTU 1280 macro 120 MTU); /* MTU size */
|
D | hdlc_rcp_if_uart.c | 209 #define MTU 1280 macro 219 MTU); /* MTU size */
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | Kconfig.l2cap | 29 int "Maximum supported L2CAP MTU for L2CAP TX buffers" 45 Maximum L2CAP MTU for L2CAP TX buffers. 76 Enable API for explicit reconfiguration of an L2CAP channel's MTU and
|
/Zephyr-latest/doc/connectivity/bluetooth/shell/host/ |
D | gatt.rst | 23 Another option available through the GATT command is initiating the MTU exchange. To do it, use the 24 :code:`gatt exchange-mtu` command. To update the shell maximum MTU, you need to update Kconfig
|
/Zephyr-latest/soc/ambiq/apollo3x/ |
D | Kconfig.defconfig.apollo3p_blue | 30 # L2CAP SDU/PDU TX MTU
|
D | Kconfig.defconfig.apollo3_blue | 30 # L2CAP SDU/PDU TX MTU
|
/Zephyr-latest/boards/ambiq/apollo4p_blue_kxr_evb/ |
D | Kconfig.defconfig | 34 # L2CAP SDU/PDU TX MTU
|
/Zephyr-latest/subsys/bluetooth/services/ots/ |
D | Kconfig | 95 int "Size of TX MTU for Object Transfer Channel" 100 int "Size of RX MTU for Object Transfer Channel" 101 # RX MTU will be truncated to account for the L2CAP PDU and SDU header.
|
/Zephyr-latest/subsys/bluetooth/ |
D | Kconfig.iso | 103 int "Maximum supported MTU for Isochronous TX buffers" 107 Maximum MTU for Isochronous channels TX buffers. 122 int "Maximum supported MTU for Isochronous RX buffers" 126 Maximum MTU for Isochronous channels RX buffers.
|
/Zephyr-latest/samples/bluetooth/channel_sounding/ |
D | README.rst | 66 MTU exchange success (247) 84 MTU exchange success (247) 103 MTU exchange success (247) 119 MTU exchange success (247)
|
/Zephyr-latest/drivers/net/ |
D | Kconfig | 32 int "PPP MTU and MRU" 35 This options sets MTU and MRU for PPP link. 202 int "MTU for loopback interface" 205 This option sets the MTU for loopback interface.
|
/Zephyr-latest/drivers/ieee802154/ |
D | ieee802154_b91.c | 637 #define MTU 125 macro 641 #define MTU 1280 macro 649 &b91_radio_api, L2, L2_CTX_TYPE, MTU);
|
D | ieee802154_cc13xx_cc26xx.c | 811 #define MTU IEEE802154_MTU macro 815 #define MTU 1280 macro 823 L2_CTX_TYPE, MTU);
|
/Zephyr-latest/doc/connectivity/networking/ |
D | eth_bridge_native_sim_setup.rst | 94 MTU : 1500 104 MTU : 1500 134 MTU : 1500
|
/Zephyr-latest/drivers/wifi/simplelink/ |
D | Kconfig.simplelink | 22 # MTU (ipv4) per: http://www.ti.com/lit/ug/swru455d/swru455d.pdf:
|
/Zephyr-latest/subsys/net/ip/ |
D | Kconfig.ipv4 | 128 outgoing packets to the MTU (1500 bytes for Ethernet). If you enable 164 bool "IPv4 Path MTU Discovery" 166 Enables IPv4 Path MTU Discovery (see RFC 1191)
|
D | Kconfig.stats | 65 Keep track of IPv6 Path MTU Discovery related statistics 72 Keep track of IPv4 Path MTU Discovery related statistics
|
/Zephyr-latest/subsys/mgmt/mcumgr/transport/ |
D | Kconfig.shell | 24 int "Shell SMP MTU"
|
D | Kconfig.uart | 56 int "UART SMP MTU"
|
D | Kconfig.udp | 57 int "UDP SMP MTU"
|
D | Kconfig | 47 MCUMGR_TRANSPORT_NETBUF_SIZE >= transport-specific-MTU + transport-overhead
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_pkt.rst | 100 know the MTU and then the family and protocol for the headers space 101 (if only these 2 are specified). If the whole fits within the MTU, 103 the headers space. If there is insufficient MTU space, the requested 105 fit within the MTU. 107 For instance, on an Ethernet network interface, with an MTU of 1500 137 will allocate 1514 bytes, the MTU + Ethernet header space.
|
/Zephyr-latest/subsys/net/l2/ |
D | Kconfig | 41 int "MTU for the custom IEEE802154 L2"
|