Searched refs:will (Results 226 – 250 of 1633) sorted by relevance
12345678910>>...66
| /Zephyr-latest/cmake/modules/ |
| D | extensions.cmake | 194 # By default the result will be returned ready to be passed directly
344 # This test will match in case there are more generator expressions in the flag.
424 # the zephyr_library_* API then precedence will be given to the
467 # within Zephyr will be looked up.
536 # Linking with a dummy interface library will place flags later on
538 # zephyr_interface will be the first interface library that flags
576 "application mode. `${library}` will not be treated as a Zephyr library."
616 # An empty Zephyr library will generate a CMake
638 # files of this library will be accessible to the 'app' library.
653 # should exist for each interface_library and will determine if 'app'
[all …]
|
| D | soc_v2.cmake | 7 # This CMake module will set the following variables in the build system based
11 # The following variables will be defined when this CMake module completes:
|
| /Zephyr-latest/subsys/mgmt/mcumgr/smp_client/ |
| D | Kconfig | 12 This will enable SMP Request generation and response handling.
29 The time (in ms) which the SMP client will wait for a response before re-sending
|
| /Zephyr-latest/drivers/interrupt_controller/ |
| D | Kconfig.intel_vtd | 16 multi-vector support, you will need to enable this.
24 If XAPIC mode is enabled, it will avoid remapping all interrupts.
|
| /Zephyr-latest/doc/connectivity/usb/device/api/ |
| D | usb_device.rst | 14 Upon completion the registered endpoint callback will be called. Before
23 transfer API will automatically split the data transmission into one or more
|
| /Zephyr-latest/samples/sensor/max6675/ |
| D | README.rst | 40 The application will read and print sensor temperature every second. Note that
41 temperature fetch will fail if the K-thermocouple is not connected. This is
|
| /Zephyr-latest/modules/zcbor/ |
| D | Kconfig | 18 Enabling this will prevent zcbor from creating lists and maps with
19 indefinite-length arrays (it will still decode them properly).
|
| /Zephyr-latest/samples/bluetooth/direct_adv/ |
| D | README.rst | 11 to the peripheral, casual advertising will be performed. Once bonded, on every subsequent
12 boot direct advertising to the bonded central will be performed. Additionally this sample
|
| /Zephyr-latest/subsys/net/l2/virtual/ipip/ |
| D | Kconfig | 9 interface will be created that will tunnel traffic on top of
|
| /Zephyr-latest/boards/native/native_posix/ |
| D | Kconfig | 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/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 144 value will select UpdateHub-CE otherwise ``n`` selects UpdateHub Cloud.
206 one will be the host and the second one will be the device under test. The
232 one will be the host NCP and the second one will be the device under test. The
250 The app image is the application itself that will be on the board. This app
251 will connect to UpdateHub server and check for new images. The image will be
295 to make sure you are creating the right signed image. The test image will be
321 After installing uhu you will need to set the ``product-uid``. The value for
371 If everything is alright, it will print on the screen ``No update available``.
373 For ``Polling`` mode, the system will automatically register your device after
403 And then wait. The board will probe the server, check if there are any new
[all …]
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 69 This will export the current Zephyr to the CMake user package registry.
100 the following criteria will be used:
102 * A Zephyr repository application will use the Zephyr in which it is located.
111 in this example, ``hello_world`` will use ``<projects>/zephyr-workspace/zephyr``.
114 * Zephyr workspace application will use the Zephyr that share the same workspace.
125 in this example, ``my_first_app`` will use ``<projects>/zephyr-workspace/zephyr`` as this Zephyr
132 * Zephyr freestanding application will use the Zephyr registered in the CMake user package registry.
150 registry and therefore this Zephyr will be used by the Zephyr freestanding application
160 The Zephyr package selected on the first CMake invocation will be used for all subsequent
184 will require ``app`` to be built with Zephyr 2.2.0 as minimum.
[all …]
|
| /Zephyr-latest/boards/shields/g1120b0mipi/boards/ |
| D | mimxrt595_evk_mimxrt595s_cm33.overlay | 8 * so the SMARTDMA will continue functioning after deep sleep
|
| /Zephyr-latest/dts/common/ |
| D | skeleton.dtsi | 5 * add a compatible value. The bootloader will typically populate the memory
|
| /Zephyr-latest/tests/bsim/bluetooth/audio/ |
| D | README.txt | 4 This application will, based on the command line arguments, select one of
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/conn/ |
| D | README.txt | 4 This application will, based on the command line arguments, select one of
|
| /Zephyr-latest/tests/kernel/mp/ |
| D | Kconfig | 5 # Must have this on where available, otherwise the linker will place
|
| /Zephyr-latest/subsys/bluetooth/host/ |
| D | CMakeLists.txt | 86 Private security keys such as the LTK will be printed out, do not use in
98 A hardcoded OOB data set will be stored in the image, do not use in
105 A predefined, publicly available keypair intended for testing will be used.
|
| /Zephyr-latest/subsys/fs/zms/ |
| D | Kconfig | 30 Every additional entry in cache will add 8 bytes in RAM
59 This option will reduce write performance as it will need to do a research of the
|
| /Zephyr-latest/drivers/virtualization/ |
| D | Kconfig | 19 This will enable support of qemu's ivshmem device, which is also
32 This will enable support of ivshmem-doorbell, i.e. the interrupt
41 more or less than necessary. Depends on how many VMs will connect
|
| /Zephyr-latest/soc/native/inf_clock/ |
| D | Kconfig | 34 This MCU will for example have its tests command line parameters presented
35 without any prefix. Note that an MCU being primary does not imply it will be
36 the first one to boot, or even that it will boot automatically.
|
| /Zephyr-latest/doc/services/modem/ |
| D | index.rst | 23 A modem backend will internally contain an instance of a modem_pipe
27 The modem backend will return a pointer to its internal modem_pipe
28 structure when initialized, which will be used to interact with the
|
| /Zephyr-latest/doc/services/dsp/ |
| D | index.rst | 11 Currently, the API will work on any architecture but will likely not be
34 application. By default, including the CMSIS module will enable all
|
| /Zephyr-latest/.github/ISSUE_TEMPLATE/ |
| D | 007_ext-source.md | 27 List the person(s) that will be maintaining the integration of this external code
39 Long description that will help reviewers discuss suitability of the
57 will it be included via an abstraction layer with this component as a
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/enum_mgmt/ |
| D | Kconfig | 51 Selects if the stack or heap will be used for variables that are needed when processing
57 Use a fixed size stack buffer, any user-supplied values longer than this will be
60 Note that stack usage for parameter storage alone will be
81 for the allocation then the request will be rejected.
|
12345678910>>...66
