Home
last modified time | relevance | path

Searched refs:existing (Results 1 – 25 of 181) sorted by relevance

12345678

/Zephyr-latest/doc/project/
Dproposals.rst10 Changes to existing features that are not considered a bug and would not
25 A request or plan to port an existing feature or enhancement to a particular
28 API for an existing hardware platform.
46 Items are examined for similarity with existing features, how they fit with
84 can help the project present its plan in a compelling way to existing and new
/Zephyr-latest/samples/subsys/fs/littlefs/
DKconfig9 Use this to force an existing file system to be created.
/Zephyr-latest/doc/connectivity/usb/device_next/api/
Dudc.rst11 It is a replacement for :ref:`usb_dc_api`. If you wish to port an existing
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D002_enhancement.md3 about: Suggest enhancements to existing features
/Zephyr-latest/tests/kernel/xip/
DREADME.txt24 # but keep existing configuration info
/Zephyr-latest/tests/lib/sprintf/
DREADME.txt24 # but keep existing configuration info
/Zephyr-latest/tests/kernel/mutex/sys_mutex/
DREADME.txt24 # but keep existing configuration info
/Zephyr-latest/doc/develop/api/
Doverview.rst27 * All existing stable APIs in Zephyr will be start with version 1.0.0.
44 Version for existing APIs are initially set based on the current state of the
/Zephyr-latest/tests/crypto/tinycrypt_hmac_prng/
DREADME.txt23 # but keep existing configuration info
/Zephyr-latest/tests/arch/arm/arm_irq_vector_table/
DREADME.txt25 # but keep existing configuration info
/Zephyr-latest/tests/arch/arm/arm_sw_vector_relay/
DREADME.txt26 # but keep existing configuration info
/Zephyr-latest/drivers/espi/
DKconfig121 with the existing ports (like 80, 92, 62 etc).
149 existing ports.
166 doesn't clash with the existing ports.
177 doesn't clash with the existing ports.
/Zephyr-latest/samples/subsys/logging/ble_backend/
DREADME.rst12 with already existing apps to debug BLE connections over UART.
/Zephyr-latest/doc/contribute/
Dproposals_and_rfcs.rst21 - The modification of an existing stable API.
40 - Addition of new boards, SoCs or drivers to existing subsystems
/Zephyr-latest/subsys/net/l2/virtual/ipip/
DKconfig10 existing network interface. Application needs to attach the IPIP
/Zephyr-latest/tests/kernel/mem_protect/stackprot/
DREADME.txt24 # but keep existing configuration info
/Zephyr-latest/tests/kernel/sleep/
DREADME.txt25 # but keep existing configuration info
/Zephyr-latest/tests/lib/c_lib/common/
DREADME.txt27 # but keep existing configuration info
/Zephyr-latest/tests/crypto/tinycrypt/
DREADME.txt23 # but keep existing configuration info
/Zephyr-latest/tests/kernel/pending/
DREADME.txt25 # but keep existing configuration info
/Zephyr-latest/tests/arch/arm/arm_runtime_nmi/
DREADME.txt25 # but keep existing configuration info
/Zephyr-latest/tests/arch/arm/arm_tz_wrap_func/src/
DREADME.txt31 # but keep existing configuration info
/Zephyr-latest/doc/kernel/services/threads/
Dnothread.rst81 Some existing drivers within the listed subsystems do not work when
84 platform is low-impact. Enhancements to add support to existing
/Zephyr-latest/doc/services/sensing/
Dindex.rst20 will directly interact with existing zephyr sensor device drivers.
24 The sensing subsystem relies on Zephyr sensor device APIs (existing version or update in future)
32 algorithms in user space with virtual sensor concepts. The existing
58 * Based on Zephyr existing low-level Sensor API (reuse 100+ existing sensor device drivers)
/Zephyr-latest/tests/arch/common/ramfunc/
DREADME.txt28 # but keep existing configuration info

12345678