| /Zephyr-latest/doc/contribute/ |
| D | proposals_and_rfcs.rst | 10 design process and produce a consensus among the project stakeholders.
12 The "RFC" (request for comments) process is intended to provide a consistent and
15 Contributors and project stakeholders should consider using this process if
26 The RFC process is a great opportunity to get more eyeballs on proposals coming
31 The RFC process can also be helpful to encourage discussions about a proposed
43 The process in itself consists in creating a GitHub issue with the :ref:`RFC
|
| D | external.rst | 11 imported into Zephyr, and the process that governs the inclusion.
14 process in order to determine whether it will be accepted. These will be
36 :ref:`external-src-process` section for more details.
155 process.
157 .. _external-src-process:
159 Submission and review process
170 Follow the steps below to begin the submission process:
186 the Apache-2.0 license, the submission process is complete and the external
193 early submission process to the Zephyr governing board for further review
206 #. On approval of the Zephyr TSC and governing board the submission process is
[all …]
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | iso_internal.h | 84 /* Process ISO buffer */
100 /* Process CIS Established event */
104 /* Process CIS Request event */
107 /** Process BIG complete event */
110 /** Process BIG terminate event */
113 /** Process BIG sync established event */
116 /** Process BIG sync lost event */
138 /* Process incoming data for a connection */
|
| /Zephyr-latest/doc/security/ |
| D | security-overview.rst | 10 defined security process that helps developers build more secure
12 the key ideas of the security process and outlines which documents need
13 to be created. After the process is implemented and all supporting
20 We begin with an overview of the Zephyr development process, which
23 In subsequent sections, the individual parts of the process are treated
27 development process that ensures adherence to relevant coding
35 Finally, a process shall be defined for reporting, classifying,
43 .. figure:: media/security-process-steps.png
45 Figure 1. Security Process Steps
50 This document is a guideline for the development of a security process
[all …]
|
| D | hardening-tool.rst | 7 process, known as "hardening", involves strengthening the security of a system to protect it from
10 At a high-level, hardening a Zephyr application can be seen as a two-fold process:
18 To simplify this process, Zephyr offers a **hardening tool** designed to analyze an application's
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | provisioning.rst | 6 Provisioning is the process of adding devices to a mesh network. It requires
12 Provisioning process. Before the provisioning process starts, the
19 The Provisioning process
25 Provisioning is a five-step process, involving the following steps:
36 To start the provisioning process, the unprovisioned device must first start
74 The provisioner initiates the Provisioning process by sending a Provisioning
86 Before the provisioning process can begin, the provisioner and the unprovisioned
89 In-band public key exchange is a part of the provisioning process and always
101 for each Provisioning process.
106 process is started by initializing pointers to
[all …]
|
| /Zephyr-latest/lib/posix/options/ |
| D | multi_process.c | 13 * a PID of zero is used to indicate that the process exists in another namespace. in getpid()
15 * PID one is usually reserved for the init process. in getpid()
17 * to send signals to process groups in some implementations. in getpid()
|
| /Zephyr-latest/boards/native/native_posix/ |
| D | Kconfig | 12 Will produce a console Linux process which can be executed natively.
26 When selected the execution of the process will be slowed down to real time.
28 If deselected, the process will run as fast as possible.
|
| /Zephyr-latest/boards/native/nrf_bsim/ |
| D | Kconfig | 12 Will produce a console Linux process which can be executed natively.
23 Will produce a console Linux process which can be executed natively.
34 Will produce a console Linux process which can be executed natively.
45 Will produce a console Linux process which can be executed natively.
|
| /Zephyr-latest/include/zephyr/mgmt/mcumgr/transport/ |
| D | smp_shell.h | 31 * @brief Attempt to process received bytes as part of an SMP frame.
37 * @param bytes Buffer with bytes to process
38 * @param size Number of bytes to process
|
| /Zephyr-latest/boards/native/native_sim/ |
| D | Kconfig | 13 Will produce a console Linux process which can be executed natively.
34 When selected the execution of the process will be slowed down to real time.
36 If deselected, the process will run as fast as possible.
|
| /Zephyr-latest/.github/ |
| D | SECURITY.md | 19 ## Reporting process
23 page for details on the process.
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | log_backend_semihost.c | 44 static void process(const struct log_backend *const backend, union log_msg_generic *msg) in process() function
64 .process = process,
|
| D | log_backend_efi_console.c | 41 static void process(const struct log_backend *const backend, in process() function
81 .process = process,
|
| D | log_backend_xtensa_sim.c | 40 static void process(const struct log_backend *const backend, in process() function
69 .process = process,
|
| D | log_backend_native_posix.c | 73 static void process(const struct log_backend *const backend, in process() function
90 .process = process,
|
| D | log_backend_adsp.c | 73 static void process(const struct log_backend *const backend, in process() function
92 .process = process,
|
| /Zephyr-latest/include/zephyr/logging/ |
| D | log_output_dict.h | 50 /** @brief Process log messages v2 for dictionary-based logging.
53 * process formatted string and output the data.
62 /** @brief Process dropped messages indication for dictionary-based logging.
|
| D | log_output.h | 82 * @note If the log output function cannot process all of the data, it is
136 /** @brief Process log messages v2 to readable strings.
139 * process formatted string and output the data.
148 /** @brief Process input data to a readable string.
172 /** @brief Process log messages v2 to SYS-T format.
175 * process formatted string and output the data in sys-t log output format.
184 /** @brief Process dropped messages indication.
|
| /Zephyr-latest/scripts/utils/ |
| D | twister_to_list.py | 32 def process(conf): function
61 update |= process(common)
64 update |= process(spec)
|
| /Zephyr-latest/samples/subsys/zbus/benchmark/ |
| D | benchmark_256KB.robot | 2 Library Process
36 ${result} Run Process west build -t ${type}_report shell=True
48 ${result} Run Process west flash shell=True
62 ${result} Run Process
|
| /Zephyr-latest/drivers/clock_control/ |
| D | nrf_clock_calibration.c | 18 * - calibration - overall process of LFRC clock calibration which is performed
23 * - process - calibration process which may consists of hf XTAL clock
30 * is ongoing, it is requested by the calibration process and released when
147 * that it is not released while calibration process in ongoing. in start_cal_process()
148 * If system releases the clock during calibration process it in start_cal_process()
149 * will be released at the end of calibration process and in start_cal_process()
|
| /Zephyr-latest/cmake/util/ |
| D | execute_process.cmake | 4 # "ARGS" for the process command-line arguments.
42 message(FATAL_ERROR "Process failed: '${ret}'")
|
| /Zephyr-latest/scripts/pylib/pytest-twister-harness/src/twister_harness/device/ |
| D | hardware_adapter.py | 111 process = stdout = None
113 …process = subprocess.Popen(self.command, stdout=subprocess.PIPE, stderr=subprocess.STDOUT, env=sel…
114 stdout, _ = process.communicate(timeout=self._flashing_timeout)
116 process.kill()
131 if process is not None and process.returncode == 0:
160 """Open a pty pair, run process and return tty name"""
191 """Terminate the process opened for serial pty script"""
195 logger.debug('Process %s terminated', self.device_config.serial_pty)
|
| /Zephyr-latest/subsys/net/lib/dhcpv4/ |
| D | dhcpv4_internal.h | 27 * acquisition or renewal process
125 * module to process.
128 * pass it through for the DHCPv4 module to process, before the actual
131 * the interface and the packet is destined for the DHCPv4 module to process.
|
