Home
last modified time | relevance | path

Searched refs:were (Results 1 – 25 of 136) sorted by relevance

123456

/Zephyr-latest/arch/posix/
DLinux.aarch64.cmake21 "If you were targeting native_sim/native/64, target native_sim instead.\n"
30 "If you were targeting native_sim, target native_sim/native/64 instead.\n"
/Zephyr-latest/boards/native/common/extra_args/
DKconfig8 Extra command line options/arguments which will be handled like if they were passed to the
/Zephyr-latest/doc/services/crypto/
Dindex.rst8 behind the operation of the different algorithms and how they were implemented.
/Zephyr-latest/doc/connectivity/networking/
Dindex.rst8 operation of the stacks and how they were implemented.
/Zephyr-latest/doc/develop/west/
Dwhy.rst12 During the development of west, a set of :ref:`west-design-constraints` were
43 Existing tools were considered during west's initial design and development.
44 None were found suitable for Zephyr's requirements. In particular, these were
96 were already conveniently available, there would be no reason to
Dwest-apis.rst140 .. NOTE: the following 'method' (not 'automethod') directives were added for
181 These were introduced to enable a transition from the deprecated
280 can be used from multiple workspaces. They were deprecated in west v0.13.0.
375 All arguments were made keyword-only. The *source_file* argument was
394 The *manifest_path* and *topdir* arguments were removed.
400 The *manifest_path* and *topdir* arguments were removed.
460 The parameters were incompatibly changed from previous versions.
Dalias.rst13 parameters as they were passed to the original command. Spaces are considered
Dinstall.rst22 binary and related files were installed.
/Zephyr-latest/doc/connectivity/bluetooth/
Dindex.rst8 operation of the layers and how they were implemented.
/Zephyr-latest/lib/posix/options/getopt/
DREADME9 [So far Zephyr samples were using getopt implementation from: argtable3.c.]
25 Originally this function was using global variables which were defining
/Zephyr-latest/doc/security/standards/
Dindex.rst6 For a long period organizations were, more or less, left responsible to deal
/Zephyr-latest/samples/basic/hash_map/
DREADME.rst13 * replaces up to the same number that were previously inserted
/Zephyr-latest/samples/drivers/uart/passthrough/
DREADME.rst11 and the processor were not present. Data read from the console is transmitted
/Zephyr-latest/include/zephyr/linker/
Dintlist.ld17 * Which indicates the memory address of the number of isrs that were
/Zephyr-latest/doc/templates/
Dsample.tmpl5 Short text description of the sample. It is recommended to word this as if you were completing
/Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/
DREADME.txt15 These tests were written to increase test coverage for the Watchdog driver.
20 These tests were prepared on a target that had a bug in the wdt_disable()
/Zephyr-latest/samples/modules/tflite-micro/magic_wand/train/
DREADME.md19 Three magic gestures were chosen, and data were collected from 7
20 different people. Some random long movement sequences were collected and divided
/Zephyr-latest/doc/kernel/iterable_sections/
Dindex.rst64 they were defined in the code.
/Zephyr-latest/doc/releases/
Dmigration-guide-3.6.rst24 * Until now ``_POSIX_C_SOURCE``, ``_XOPEN_SOURCE``, and ``_XOPEN_SOURCE_EXTENDED`` were defined
117 were removed. These are listed in the following table. The table also
210 * The io-channel cells of the following devicetree bindings were reduced from 2 (``positive`` and
224 :dtcompatible:`microchip,mcp3208` devicetree bindings were renamed from ``channel`` to the common
254 can_driver_config``) and data (``struct can_driver_data``) fields were introduced. Out-of-tree CAN
272 Transmission Request (RTR) frames were removed since not all CAN controllers implement support for
386 :dtcompatible:`goodix,gt911` were using the incorrect polarity for the
455 If extra ATT buffers were configured using :kconfig:option:`CONFIG_BT_L2CAP_TX_BUF_COUNT`,
482 * The ``CONFIG_BT_HCI_RESERVE`` and ``CONFIG_BT_HCI_RAW_RESERVE`` Kconfig options were removed. All
574 The APIs were marked as callable from usermode but in practice this does not work as the device
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Drpr_cli.rst132 while the new address is set to 0x0009. If the two addresses were the same, and the
134 Refresh procedure. If the two addresses were the same, and the ``composition_changed`` flag was set
/Zephyr-latest/share/zephyr-package/cmake/
DZephyrConfigVersion.cmake19 …message("\n The following Zephyr repository configuration file were considered but not accepted:")
138 # Ending here means there were no candidates in workspace of the app.
/Zephyr-latest/boards/lowrisc/opentitan_earlgrey/doc/
Dindex.rst58 following steps were tested on OpenTitan master branch @ 6a3c2e98.
/Zephyr-latest/
DCODE_OF_CONDUCT.md125 The only changes made by The Zephyr Project to the original document were to
128 Community Impact Guidelines were inspired by
/Zephyr-latest/samples/arch/smp/pktqueue/
DREADME.rst84 All 20000 packet headers were processed in 89 msec
/Zephyr-latest/cmake/modules/
Dwest.cmake75 # Set WEST to a COMMAND prefix as if it were a find_program() result, and

123456