Searched refs:there (Results 51 – 75 of 423) sorted by relevance
12345678910>>...17
/Zephyr-latest/boards/microchip/mec15xxevb_assy6853/ |
D | CMakeLists.txt | 15 # but there is no tool for Apple. So
|
/Zephyr-latest/boards/microchip/mec172xevb_assy6906/ |
D | CMakeLists.txt | 15 # but there is no tool for Apple. So
|
/Zephyr-latest/drivers/syscon/ |
D | Kconfig | 17 extract information from there.
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | socks5.rst | 49 For MQTT client, there is :c:func:`mqtt_client_set_proxy()` API that the
|
D | ieee802154.rst | 62 IEEE802154/ieee802154 prefixes there. 97 documented there.
|
/Zephyr-latest/drivers/dma/ |
D | Kconfig.nxp_sof_host_dma | 29 configuration doesn't make much sense as there's
|
D | Kconfig.dw_common | 16 LLI struct pool. If during dma_config() a log notes there are not enough LLI structs
|
/Zephyr-latest/doc/hardware/peripherals/ |
D | regulators.rst | 16 The simplest case where a regulator is needed is one where there is only one
|
D | i3c.rst | 28 Due to the nature of the I3C, there are devices on the bus where 97 #. Do ``ENTDAA`` to start dynamic address assignment, if there are 100 * If there is a device waiting for address, it will send 104 * If there is a match, assign an address (either from 111 * If there is no match, depending on policy, it can be 119 * This step can be skipped if there is no connected devices 154 * Note that there are usually limited IBI slots on
|
/Zephyr-latest/boards/native/native_posix/ |
D | Kconfig | 27 (if there is a lot of load it may be slower than real time)
|
/Zephyr-latest/share/zephyr-package/cmake/ |
D | ZephyrConfig.cmake | 132 …# This means this Zephyr is likely the correct one, but there could be an alternative installed al… 133 # Thus, check if there is an even better candidate. 154 # Ending here means there were no candidates in workspace of the app.
|
/Zephyr-latest/doc/services/storage/nvs/ |
D | nvs.rst | 13 The id is a 16-bit unsigned number. NVS ensures that for each used id there is 45 To protect the flash area against frequent erases it is important that there is 47 endless loop of flash page erases when there is limited free space. When such 48 a loop is detected NVS returns that there is no more space available.
|
/Zephyr-latest/drivers/serial/ |
D | Kconfig.xen | 27 privileged domain. Thus, there is no console daemon and Xen
|
/Zephyr-latest/doc/hardware/arch/ |
D | risc-v.rst | 8 Currently, there's support for some boards, as well as Qemu support
|
/Zephyr-latest/drivers/entropy/ |
D | Kconfig | 46 to signal that there is a true entropy driver.
|
/Zephyr-latest/share/sysbuild/cmake/modules/ |
D | sysbuild_kconfig.cmake | 67 # We only want to set this in cache it has been defined and is not already there. 75 # If there is no SB_CONF_FILE, then use empty.conf to make kconfiglib happy.
|
/Zephyr-latest/doc/develop/languages/c/ |
D | picolibc.rst | 31 When built as a Zephyr module, there are several configuration knobs 68 For toolchain where there is no bundled Picolibc, it is still 85 when there is no toolchain bundled Picolibc.
|
/Zephyr-latest/scripts/coccinelle/ |
D | array_size.cocci | 4 //# where there is a division of sizeof the array by the sizeof its first
|
/Zephyr-latest/samples/net/virtual/ |
D | README.rst | 17 On top of Ethernet interface there are two virtual network interfaces,
|
/Zephyr-latest/tests/bsim/bluetooth/ll/cis/ |
D | Kconfig | 54 When CIS is created first, there isn't sufficient time available for
|
/Zephyr-latest/subsys/storage/flash_map/ |
D | Kconfig | 35 If enabled, there will be available the backend to check flash
|
/Zephyr-latest/doc/connectivity/networking/ |
D | networking_with_host.rst | 62 requires that there is an adaptation driver in Zephyr for interfacing 81 * Here, two Zephyr instances are running and there is IEEE 802.15.4 link layer
|
/Zephyr-latest/doc/safety/ |
D | safety_requirements.rst | 65 The CI in the PR will check if the requirements UIDs are valid or if there are duplicates in it. 66 If there are duplicates in the PR, these need to be resolved by rebasing and re-executing
|
/Zephyr-latest/doc/connectivity/bluetooth/api/ |
D | gatt.rst | 59 alternatively there is :c:func:`bt_gatt_notify_cb` where it is possible to 91 the same attribute are supported so there could be multiple ``notify`` callback
|
/Zephyr-latest/doc/develop/west/ |
D | moving-to-west.rst | 23 and change directory there.
|
12345678910>>...17