| /Zephyr-Core-3.5.0/arch/arm64/core/xen/ |
| D | CMakeLists.txt | 4 # Needed to separate definitions in common Xen headers
7 # Xen interface version used in headers for correct definition
|
| /Zephyr-Core-3.5.0/subsys/usb/device/class/netusb/ |
| D | CMakeLists.txt | 6 # USB headers
12 # IP headers
|
| /Zephyr-Core-3.5.0/samples/arch/smp/pktqueue/ |
| D | README.rst | 17 of packet headers is initialized. Each header contains some random data of size
38 The headers then are stored in multiple "sender" queues (the number is defined
47 As soon as all headers in each pair of queues are moved from "sender" to
57 the number of headers in queue (``SIZE_OF_QUEUE``), and
63 This project outputs total time required for processing all packet headers.
79 Each of 2 parallel queues is processed by 3 threads on 2 cores and contain 5000 packet headers.
84 All 20000 packet headers were processed in 89 msec
|
| /Zephyr-Core-3.5.0/tests/net/lib/lwm2m/interop/pytest/ |
| D | leshan.py | 40 def put_raw(self, path: str, data: str | dict | None = None, headers: dict | None = None):
41 resp = requests.put(f'{self.api_url}{path}', data=data, headers=headers)
47 …}?timeout={self.timeout}&format={self.format}' + uri_options, data=data, headers={'content-type': …
50 …resp = requests.post(f'{self.api_url}{path}', data=data, headers={'content-type': 'application/jso…
|
| /Zephyr-Core-3.5.0/boards/shields/arduino_uno_click/doc/ |
| D | index.rst | 9 The Arduino UNO click is an extension to the Arduino UNO R3 headers.
10 It's a simple shield that converts Arduino UNO R3 headers to two mikroBUS
16 Two mikroBUS headers are exposed by the overlay: ``mikrobus_header_1`` and
|
| /Zephyr-Core-3.5.0/include/zephyr/ |
| D | kernel_includes.h | 17 #error Please do not include kernel-specific headers directly, use <zephyr/kernel.h> instead
|
| /Zephyr-Core-3.5.0/subsys/usb/device/class/hid/ |
| D | CMakeLists.txt | 6 # USB headers
|
| /Zephyr-Core-3.5.0/include/zephyr/toolchain/ |
| D | armclang.h | 11 #error Please do not include toolchain-specific headers directly, use <zephyr/toolchain.h> instead
|
| D | llvm.h | 11 #error Please do not include toolchain-specific headers directly, use <zephyr/toolchain.h> instead
|
| /Zephyr-Core-3.5.0/drivers/wifi/eswifi/ |
| D | CMakeLists.txt | 6 # IP headers
|
| /Zephyr-Core-3.5.0/boards/arm/npcx7m6fb_evb/doc/ |
| D | index.rst | 22 - ADC & GPIO headers
26 - Intel Modular Embedded Controller Card (MECC) headers
82 If the correct IDC headers are installed, this board supports both J-TAG and
|
| /Zephyr-Core-3.5.0/boards/arm/npcx9m6f_evb/doc/ |
| D | index.rst | 22 - ADC & GPIO headers
26 - Intel Modular Embedded Controller Card (MECC) headers
96 If the correct IDC headers are installed, this board supports both J-TAG and
|
| /Zephyr-Core-3.5.0/samples/net/sockets/http_client/src/ |
| D | main.c | 310 const char *headers[] = { in run_queries() local
322 req.header_fields = headers; in run_queries()
334 const char *headers[] = { in run_queries() local
346 req.header_fields = headers; in run_queries()
|
| /Zephyr-Core-3.5.0/boards/arm/npcx4m8f_evb/doc/ |
| D | index.rst | 22 - ADC & GPIO headers
26 - Intel Modular Embedded Controller Card (MECC) headers
95 If the correct headers are installed, this board supports both J-TAG and also
|
| /Zephyr-Core-3.5.0/boards/shields/wnc_m14a2a/boards/ |
| D | frdm_k64f.overlay | 9 * headers. It needs to be defined individually.
|
| D | nrf52840dk_nrf52840.overlay | 30 * headers. It needs to be defined individually.
|
| /Zephyr-Core-3.5.0/modules/thrift/cmake/ |
| D | thrift.cmake | 10 target # CMake target (for dependencies / headers)
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | net_pkt.rst | 28 more specifically from the headers to the payload.
100 know the MTU and then the family and protocol for the headers space
103 the headers space. If there is insufficient MTU space, the requested
104 size will be shrunk so the possible headers space and new size will
122 UDP headers) will not be used for the payload.
270 Or, if headers space needs to be accounted for, call:
291 contiguously, especially with network packets which embed headers.
293 These headers are, most of the time, a known fixed set of bytes. It is
311 Let's take the example of IP and UDP. Both IPv4 and IPv6 headers are
335 the requested data. On the RX path, these headers will be read but not
|
| /Zephyr-Core-3.5.0/samples/arch/smp/pktqueue/src/ |
| D | main.c | 29 uint8_t headers[QUEUE_NUM][SIZE_OF_QUEUE][SIZE_OF_HEADER]; variable
43 descriptors[queue_num][i].ptr = (uint8_t *)&headers[queue_num][i]; in init_datagram_queue()
|
| /Zephyr-Core-3.5.0/boards/arm/nrf52832_mdk/doc/ |
| D | index.rst | 13 The kit gives access to 24 I/Os and interfaces via headers and has a
|
| /Zephyr-Core-3.5.0/boards/shields/esp_8266/doc/ |
| D | index.rst | 52 Sometimes boards declare standard headers like Arduino R3 but not define
97 configurations should be used based on the board standard headers available.
123 To build shield with standard headers:
|
| /Zephyr-Core-3.5.0/modules/hal_gigadevice/ |
| D | CMakeLists.txt | 41 # GD32E50X series HAL public headers require extra definitions
49 # GD32A50X series HAL public headers require extra definitions
|
| /Zephyr-Core-3.5.0/samples/net/sockets/packet/ |
| D | README.rst | 13 The Zephyr network subsystem does not touch any of the headers
|
| /Zephyr-Core-3.5.0/samples/subsys/display/cfb_custom_font/ |
| D | README.rst | 10 font headers automatically at build time.
|
| /Zephyr-Core-3.5.0/cmake/compiler/xt-clang/ |
| D | compiler_flags.cmake | 5 # nostdinc_include contains path to llvm headers and also relative
|
