Home
last modified time | relevance | path

Searched refs:new (Results 1 – 25 of 434) sorted by relevance

12345678910>>...18

/Zephyr-Core-3.7.0/boards/arm/fvp_baser_aemv8r/doc/
Ddebug-with-arm-ds.rst37 Create a new configuration database
40 Create a new configuration database by selecting ``File -> New -> Other... -> Configuration Databas…
42 .. image:: images/create-new-configuration-database.jpg
44 :alt: Arm DS create new configuration database
48 .. image:: images/create-new-configuration-database_database-name.jpg
50 :alt: Arm DS create new configuration database: choose database name
52 Click ``Finish`` and the new configuration database can be seen in ``Project Explorer``:
54 .. image:: images/create-new-configuration-database_shown-in-project-explorer.jpg
56 :alt: Arm DS create new configuration database: shown in project explorer
58 Create a new model configuration
[all …]
/Zephyr-Core-3.7.0/modules/thrift/src/thrift/server/
DTServer.h168 std::shared_ptr<TTransportFactory>(new TTransportFactory())); in TServer()
170 std::shared_ptr<TTransportFactory>(new TTransportFactory())); in TServer()
172 std::shared_ptr<TProtocolFactory>(new TBinaryProtocolFactory())); in TServer()
174 std::shared_ptr<TProtocolFactory>(new TBinaryProtocolFactory())); in TServer()
178 : processorFactory_(new TSingletonProcessorFactory(processor)) in TServer()
181 std::shared_ptr<TTransportFactory>(new TTransportFactory())); in TServer()
183 std::shared_ptr<TTransportFactory>(new TTransportFactory())); in TServer()
185 std::shared_ptr<TProtocolFactory>(new TBinaryProtocolFactory())); in TServer()
187 std::shared_ptr<TProtocolFactory>(new TBinaryProtocolFactory())); in TServer()
195 std::shared_ptr<TTransportFactory>(new TTransportFactory())); in TServer()
[all …]
/Zephyr-Core-3.7.0/subsys/net/l2/ppp/
Dmisc.c45 enum ppp_phase new) in validate_phase_transition() argument
61 if (!(valid_transitions[current] & 1 << new)) { in validate_phase_transition()
64 ppp_phase_str(new), new); in validate_phase_transition()
69 enum ppp_phase new) in validate_phase_transition() argument
72 ARG_UNUSED(new); in validate_phase_transition()
209 enum ppp_state new) in validate_state_transition() argument
252 if (!(valid_transitions[current] & 1 << new)) { in validate_state_transition()
255 ppp_state_str(new), new); in validate_state_transition()
260 enum ppp_state new) in validate_state_transition() argument
263 ARG_UNUSED(new); in validate_state_transition()
/Zephyr-Core-3.7.0/arch/arm64/include/
Dkernel_arch_func.h37 extern void z_arm64_context_switch(struct k_thread *new, in arch_switch()
39 struct k_thread *new = switch_to; in arch_switch() local
43 z_arm64_context_switch(new, old); in arch_switch()
/Zephyr-Core-3.7.0/arch/arm/include/cortex_a_r/
Dkernel_arch_func.h45 extern void z_arm_context_switch(struct k_thread *new, in arch_switch()
48 struct k_thread *new = switch_to; in arch_switch() local
52 z_arm_context_switch(new, old); in arch_switch()
/Zephyr-Core-3.7.0/include/zephyr/xen/
Dgeneric.h29 #define synch_cmpxchg(ptr, old, new) \ argument
31 __atomic_compare_exchange_n(ptr, &stored, new, 0, __ATOMIC_SEQ_CST, \
32 __ATOMIC_SEQ_CST) ? new : old; \
/Zephyr-Core-3.7.0/tests/net/lib/mqtt_packet/
DREADME41 [PASS] 1 - CONNECT, new session, zeros
42 [PASS] 2 - CONNECT, new session, will
43 [PASS] 3 - CONNECT, new session, will retain
44 [PASS] 4 - CONNECT, new session, will qos = 1
45 [PASS] 5 - CONNECT, new session, will qos = 1, will retain
46 [PASS] 6 - CONNECT, new session, username and password
/Zephyr-Core-3.7.0/tests/bsim/bluetooth/mesh/tests_scripts/persistence/
Daccess.sh24 -- -argstest access-cfg=new-subs
28 -- -argstest access-cfg=new-subs
47 -- -argstest access-cfg=new-subs
51 -- -argstest access-cfg=new-subs
/Zephyr-Core-3.7.0/arch/riscv/include/
Dkernel_arch_func.h61 extern void z_riscv_switch(struct k_thread *new, struct k_thread *old); in arch_switch()
62 struct k_thread *new = switch_to; in arch_switch() local
66 arch_syscall_invoke2((uintptr_t)new, (uintptr_t)old, RV_ECALL_SCHEDULE); in arch_switch()
68 z_riscv_switch(new, old); in arch_switch()
/Zephyr-Core-3.7.0/doc/releases/
Drelease-notes-3.5.rst14 * Added new battery charger driver API
15 * Added new hardware spinlock driver API
16 * Added new modem subsystem
17 * Added support for 45+ new boards
130 * For the new boards, embedded C libraries can be used, and conflicts with the host symbols
132 * The :ref:`POSIX OS abstraction<posix_support>` is supported in these new boards.
185 * Added new API to manage Bluetooth settings storage
435 * Added a new ``initlevels`` target for printing the final device and
581 * A new mandatory method attr_get() was introduced into ieee802154_radio_api.
589 by the standard conforming new driver attribute
[all …]
Drelease-notes-3.3.rst39 :c:macro:`DEVICE_DT_DEFINE`. It also includes a new backend API pointer to
66 removed in favor of new :dtcompatible:`zephyr,flash-disk` devicetree binding.
160 This should now be configured using the new ``lse_bypass`` property of
303 use the new API by following the :ref:`migration guide <mcumgr_cb_migration>`
414 * Added a new ``BT_CONN_INTERVAL_TO_US`` utility macro.
422 * Added a new :c:func:`bt_le_per_adv_sync_lookup_index` function.
434 * Added a new :kconfig:option:`BT_ID_ALLOW_UNAUTH_OVERWRITE` that allows
464 * Added a new ``LL_ASSERT_MSG`` macro for verbose assertions.
668 * Removed :c:macro:`BOOT_TRAILER_IMG_STATUS_OFFS` in favor a two new functions;
745 * STM32: Flash driver was revisited to simplify reuse of driver for new series, taking
[all …]
/Zephyr-Core-3.7.0/doc/contribute/
Dproposals_and_rfcs.rst13 controlled path for new features to enter the project.
19 - A new feature that creates new API surface area, and would require a feature
23 - The introduction of new idiomatic usage or conventions, even if they do not
40 - Addition of new boards, SoCs or drivers to existing subsystems
46 guideline to write a new RFC.
/Zephyr-Core-3.7.0/subsys/logging/
DKconfig.template.log_config_inherit9 # Name of the new log module.
12 # Name of the module that will be inherited by the new module.
/Zephyr-Core-3.7.0/scripts/build/
Dparse_syscalls.py143 def update_file_if_changed(path, new): argument
148 if new != old:
150 fp.write(new)
153 fp.write(new)
/Zephyr-Core-3.7.0/doc/project/
Dproposals.rst6 For feature tracking we use Github labels to classify new features and
15 A request for the implementation or inclusion of a new unit of functionality
26 hardware platform. This ranges from porting Zephyr itself to a new
36 This is the formal way for asking for a new feature in Zephyr and indicating its
44 - Label new features requests as ``feature-request``
45 - The TSC discusses new ``feature-request`` items regularly and triages them.
84 can help the project present its plan in a compelling way to existing and new
85 stakeholders, to help recruit new members and it can be a helpful resource the
Dcode_flow.rst16 of new features to be introduced into the main branch when ready. Creating a new
20 Zephyr, the introduction of fixes and new features, if approved by the TSC,
37 possible to initiate in-depth discussions around new additions before
/Zephyr-Core-3.7.0/samples/modules/tflite-micro/magic_wand/train/
DREADME.md62 but inferior performance on new data.
75 performance on new data.
90 ## Collecting new data
92 To obtain new training data using the
141 First, in a new terminal window, run the following command to begin logging
157 Press the `RST` button to start capturing a new gesture, then press Button 14
177 Edit the following files to include your new gesture names (replacing
184 Edit the following files to include your new person names (replacing "hyw",
191 Finally, run the commands described earlier to train a new model.
/Zephyr-Core-3.7.0/.github/ISSUE_TEMPLATE/
D008_bin-blobs.md31 you are submitting this as part of a new module you may link to the same Pull
32 Request that introduced the new module.
/Zephyr-Core-3.7.0/doc/hardware/porting/
Dindex.rst6 These pages document how to port Zephyr to new hardware.
/Zephyr-Core-3.7.0/doc/develop/west/
Drelease-notes.rst67 - ``west.commands.WestCommand.run_subprocess()``: new wrapper
86 - ``west compare``: new command that compares the state of the
89 - Support for a new ``manifest.project-filter`` configuration option.
95 warnings. These warnings are errors if the new ``manifest.project-filter``
155 add new options with similar names but different behavior to existing ones.
161 - ``west update``: new ``--submodule-init-config`` option.
188 - The :ref:`west-apis-commands` module got some new APIs which lay groundwork
215 in a new workspace for the first time; this used to fail (just for the first
268 - ``west.configuration.Configuration``: new object-oriented interface to the
275 - ``config``: new attribute, returns a ``Configuration`` object or aborts the
[all …]
/Zephyr-Core-3.7.0/doc/services/tfm/
Dtestsuites.rst41 changes to TF-M, such as enabling a new TF-M board target, or making changes
43 before publishing a new PR for new board support, etc.
/Zephyr-Core-3.7.0/doc/connectivity/bluetooth/api/mesh/
Ddfu_srv.rst61 :ref:`bluetooth_mesh_models_rpr_srv` is supported, the Composition Data of the new firmware image
62 will be represented by Composition Data Pages 128, 129, and 130. The Models Metadata of the new
72 while the Composition Data in the new firmware will be loaded into Composition Data Pages 128, 129
74 Models Metadata for the new image will be loaded into Models Metadata Page 128.
79 and working with the old firmware after the new firmware image is applied.
115 the new firmware. The firmware image table should be updated to reflect the new firmware ID of the
120 After booting up with the new firmware, the firmware image table should be updated before the
/Zephyr-Core-3.7.0/scripts/kconfig/
Ddiffconfig130 new = sorted(b.keys())
131 for config in new:
/Zephyr-Core-3.7.0/cmake/
Dtarget_toolchain_flags.cmake15 # usage and symbolic links, then the upgraded compiler will have new version
16 # and thus generate a new signature.
35 # a new toolchain.
/Zephyr-Core-3.7.0/drivers/serial/
DKconfig.native_posix36 It is strongly discouraged to try to use this option with the new
46 When this option is selected a new command line switch is provided:
60 string "Default command to attach the UART to a new terminal"
65 run to attach a new terminal to the 1st UART.

12345678910>>...18