| /Zephyr-Core-3.7.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.7.0/subsys/usb/device/class/netusb/ |
| D | CMakeLists.txt | 6 # USB headers
12 # IP headers
|
| /Zephyr-Core-3.7.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.7.0/doc/services/llext/ |
| D | build.rst | 6 often useful to have access to the headers and compiler flags used by the main
18 needs to export the headers and compiler flags used by the main Zephyr
138 headers and compiler flags used by the main Zephyr application, since they have
139 a direct impact on how Zephyr headers are interpreted and the extension is
151 directory. It's a tarball that contains the headers and compile flags needed
152 to build extensions. The extension developer can then include the headers
167 Compiler flags to add directories containing non-autogenerated headers
172 Compiler flags to add directories containing autogenerated headers to
177 Compiler flags to add all directories containing headers used in the
183 Compiler flags for autogenerated headers that must be included in the
[all …]
|
| /Zephyr-Core-3.7.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.7.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.7.0/soc/nordic/ |
| D | CMakeLists.txt | 15 # Include dt-bindings headers into the build. This lets us validate all required
17 # headers for different SoCs.
|
| /Zephyr-Core-3.7.0/subsys/usb/device/class/hid/ |
| D | CMakeLists.txt | 6 # USB headers
|
| /Zephyr-Core-3.7.0/include/zephyr/toolchain/ |
| D | armclang.h | 11 #error Please do not include toolchain-specific headers directly, use <zephyr/toolchain.h> instead
|
| /Zephyr-Core-3.7.0/tests/net/lib/lwm2m/interop/pytest/ |
| D | leshan.py | 65 …def put_raw(self, path: str, data: str | dict | None = None, headers: dict | None = None, params: …
67 …resp = self._s.put(f'{self.api_url}{path}', data=data, headers=headers, params=params, timeout=sel…
74 …}?timeout={self.timeout}&format={self.format}' + uri_options, data=data, headers={'content-type': …
81 headers={'content-type': 'application/json'}
84 headers=None
86 …resp = self._s.post(f'{self.api_url}{path}' + uri_options, data=data, headers=headers, timeout=sel…
430 …r = requests.get(f'{self.api_url}/event?{endpoint}', stream=True, headers={'Accept': 'text/event-s…
|
| /Zephyr-Core-3.7.0/tests/modules/nanopb/lib/ |
| D | CMakeLists.txt | 8 # Add include directory to find the generated headers
|
| /Zephyr-Core-3.7.0/drivers/wifi/eswifi/ |
| D | CMakeLists.txt | 6 # IP headers
|
| /Zephyr-Core-3.7.0/boards/nuvoton/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.7.0/cmake/ |
| D | llext-edk.cmake | 4 # This script generates a tarball containing all headers and flags necessary to
5 # build an llext extension. It does so by copying all headers accessible from
10 # all necessary headers and flags. File paths are made relative to a few key
17 # - INTERFACE_INCLUDE_DIRECTORIES: List of include directories to copy headers
26 # - CONFIG_LLEXT_EDK_USERSPACE_ONLY: Whether to copy syscall headers from the
28 # supports userspace, as the syscall headers are regenerated in the edk
152 # Copy syscall headers from edk directory, as they were regenerated there.
|
| /Zephyr-Core-3.7.0/boards/nuvoton/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.7.0/tests/net/lib/http_server/core/ |
| D | CMakeLists.txt | 8 include_directories(${BASE_PATH}/headers)
|
| /Zephyr-Core-3.7.0/boards/ene/kb1200_evb/doc/ |
| D | index.rst | 19 - ADC & GPIO headers
73 If the correct headers are installed, this board supports SWD Debug Interface.
|
| /Zephyr-Core-3.7.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.7.0/boards/shields/wnc_m14a2a/boards/ |
| D | frdm_k64f.overlay | 9 * headers. It needs to be defined individually.
|
| /Zephyr-Core-3.7.0/boards/nuvoton/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.7.0/tests/net/lib/http_server/crime/ |
| D | CMakeLists.txt | 8 include_directories(${BASE_PATH}/headers)
|
| /Zephyr-Core-3.7.0/modules/thrift/cmake/ |
| D | thrift.cmake | 10 target # CMake target (for dependencies / headers)
|
| /Zephyr-Core-3.7.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.7.0/samples/arch/smp/pktqueue/src/ |
| D | main.c | 49 uint8_t headers[QUEUE_NUM][SIZE_OF_QUEUE][SIZE_OF_HEADER]; variable
63 descriptors[queue_num][i].ptr = (uint8_t *)&headers[queue_num][i]; in init_datagram_queue()
|
| /Zephyr-Core-3.7.0/boards/makerdiary/nrf52832_mdk/doc/ |
| D | index.rst | 13 The kit gives access to 24 I/Os and interfaces via headers and has a
|
