/Zephyr-latest/tests/cmake/overlays/soc_folder_kconfig/ |
D | Kconfig | 9 bool "Included board Kconfig fragment" 12 bool "Included board Kconfig fragment with suffix" 15 bool "Included board with qualifiers Kconfig fragment" 18 bool "Included other board Kconfig fragment" 21 bool "Included soc Kconfig fragment" 24 bool "Included soc overlay Kconfig fragment" 27 bool "Included other soc overlay Kconfig fragment"
|
/Zephyr-latest/doc/_doxygen/ |
D | doxygen-awesome.css | 70 --code-font-size: 14px; /* affects code, fragment */ 139 /* fragment colors */ 140 --fragment-background: #F8F9FA; 141 --fragment-foreground: #37474F; 142 --fragment-keyword: #bb6bb2; 143 --fragment-keywordtype: #8258b3; 144 --fragment-keywordflow: #d67c3b; 145 --fragment-token: #438a59; 146 --fragment-comment: #969696; 147 --fragment-link: #5383d6; [all …]
|
/Zephyr-latest/drivers/ethernet/eth_nxp_enet_qos/ |
D | eth_nxp_enet_qos_mac.c | 64 struct net_buf *fragment = pkt->frags; in eth_nxp_enet_qos_tx() local 68 while (fragment != NULL) { in eth_nxp_enet_qos_tx() 70 total_bytes += fragment->len; in eth_nxp_enet_qos_tx() 71 fragment = fragment->frags; in eth_nxp_enet_qos_tx() 97 fragment = pkt->frags; in eth_nxp_enet_qos_tx() 100 net_pkt_frag_ref(fragment); in eth_nxp_enet_qos_tx() 102 tx_desc_ptr->read.buf1_addr = (uint32_t)fragment->data; in eth_nxp_enet_qos_tx() 103 tx_desc_ptr->read.control1 = FIELD_PREP(0x3FFF, fragment->len); in eth_nxp_enet_qos_tx() 106 fragment = fragment->frags; in eth_nxp_enet_qos_tx() 138 struct net_buf *fragment = pkt->frags; in tx_dma_done() local [all …]
|
/Zephyr-latest/drivers/ethernet/ |
D | Kconfig.cyclonev | 31 Received packets are spread across the required number of fragment 32 buffers. Each RX fragment has a size of CONFIG_NET_BUF_DATA_SIZE. 33 There is one descriptor entry per fragment.
|
D | Kconfig.dwmac | 59 Received packets are spread across the required number of fragment 60 buffers. Each RX fragment has a size of CONFIG_NET_BUF_DATA_SIZE. 61 There is one descriptor entry per fragment.
|
D | Kconfig.xmc4xxx | 27 data fragment and its size. 34 data fragment and its size. The data fragments are pre-allocated from the rx
|
/Zephyr-latest/scripts/west_commands/zspdx/ |
D | cmakefileapijson.py | 234 fragment = zspdx.cmakefileapi.TargetCommandFragment() 235 fragment.fragment = fragment_dict.get("fragment", "") 236 fragment.role = fragment_dict.get("role", "") 237 target.link_commandFragments.append(fragment) 247 fragment = zspdx.cmakefileapi.TargetCommandFragment() 248 fragment.fragment = fragment_dict.get("fragment", "") 249 fragment.role = fragment_dict.get("role", "") 250 target.archive_commandFragments.append(fragment) 289 fragment = commandFragment_dict.get("fragment", "") 290 if fragment != "": [all …]
|
D | cmakefileapi.py | 132 self.fragment = ""
|
/Zephyr-latest/subsys/lorawan/services/ |
D | Kconfig | 96 this value divided by the fragment size. 106 Maximum size of one fragment transferred during the fragmented data 110 The fragment has to fit into the LoRaWAN payload, which can be up to 114 For some MCUs like the STM32WL the fragment size has to be a multiple 118 fragment size is known, use that value for MIN and MAX config to 127 Minimum size of one fragment transferred during the fragmented data 131 The fragment has to fit into the LoRaWAN payload, which can be up to 135 For some MCUs like the STM32WL the fragment size has to be a multiple 139 fragment size is known, use that value for MIN and MAX config to
|
/Zephyr-latest/tests/cmake/hwm/board_extend/oot_root/boards/native/native_sim_extend/ |
D | Kconfig | 8 This kconfig is set when the extended variant board config fragment 29 This kconfig is set when the extended variant board defconfig fragment
|
/Zephyr-latest/tests/net/ieee802154/6lo_fragment/ |
D | CMakeLists.txt | 5 project(fragment) project
|
/Zephyr-latest/tests/cmake/hwm/board_extend/ |
D | Kconfig | 8 This kconfig is set when the base board config fragment is supposed to
|
/Zephyr-latest/samples/sysbuild/with_mcuboot/ |
D | README.rst | 11 creating a image specific Kconfig fragment. 25 The :file:`sysbuild/mcuboot.conf` file will be used as an extra fragment that
|
/Zephyr-latest/doc/services/device_mgmt/ |
D | smp_transport.rst | 28 packets, the SMP header in the first fragment contains sufficient information 110 | body | no more than | Raw body data fragment | 134 | body | no more than | Raw body data fragment | 168 | body | no more than | Raw body data fragment | 181 | body | no more than | Raw body data fragment |
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | Kconfig.l2cap | 17 int "Number of L2CAP TX fragment buffers" 25 and there are no dedicated fragment buffers, a deadlock may occur.
|
/Zephyr-latest/doc/build/sysbuild/ |
D | index.rst | 607 Zephyr application Kconfig fragment and devicetree overlay 610 In the folder of the main application, create a Kconfig fragment or a devicetree 616 A Kconfig fragment could look as: 681 ``mcuboot`` will use the ``mcuboot.conf`` Kconfig fragment file and ``my_sample`` will use the 682 ``my_sample.conf`` Kconfig fragment file. Sysbuild itself will use the ``sysbuild.conf`` 683 Kconfig fragment file. 686 included, ``mcuboot`` will use the ``mcuboot_max_log.conf`` Kconfig fragment file and 687 ``my_sample`` will use the ``my_sample.conf`` Kconfig fragment file (as it will fallback to the 688 file without the suffix). Sysbuild itself will use the ``sysbuild.conf`` Kconfig fragment file 692 included, ``mcuboot`` will use the ``mcuboot.conf`` Kconfig fragment file and [all …]
|
/Zephyr-latest/subsys/modem/ |
D | Kconfig | 61 int "Network buffer fragment size"
|
/Zephyr-latest/subsys/bluetooth/ |
D | Kconfig.iso | 91 int "Number of ISO TX fragment buffers" 99 and there are no dedicated fragment buffers, a deadlock may occur.
|
/Zephyr-latest/doc/connectivity/canbus/ |
D | isotp.rst | 28 single-frames (SF). They don't need to fragment and do not have any flow-control.
|
/Zephyr-latest/cmake/modules/ |
D | soc_v1.cmake | 18 # - SOC_PATH: Path fragment defined by either SOC_NAME or SOC_FAMILY/SOC_SERIES.
|
/Zephyr-latest/samples/drivers/ipm/ipm_esp32/ |
D | README.rst | 19 message, so high level protocol is responsible to fragment larger
|
/Zephyr-latest/tests/bluetooth/controller/ctrl_isoal/ |
D | Kconfig | 42 number of buffers and maximum SDU fragment size will limit the maximum
|
/Zephyr-latest/subsys/mgmt/mcumgr/transport/ |
D | Kconfig.lorawan | 86 Will fragment messages into multiple uplink messages if they are too big to fit into a
|
/Zephyr-latest/samples/basic/button/ |
D | README.rst | 44 Here is a minimal devicetree fragment which supports this sample. This only
|
/Zephyr-latest/doc/services/storage/disk/ |
D | access.rst | 65 Example devicetree fragment below shows how to add SD card node to ``spi1``
|