Searched refs:will (Results 1 – 25 of 1633) sorted by relevance
12345678910>>...66
/Zephyr-latest/subsys/net/lib/tftp/ |
D | Kconfig | 22 int "Maximum amount of time the TFTP Client will wait for a response from the server." 25 Maximum amount of time (in msec) that the TFTP Client will wait for 27 will assume that the Server failed and close the connection. 30 int "Number of times the TFTP Client will retransmit the request to the server." 33 Once the TFTP Client sends out a request, it will wait 35 However, if it doesn't arrive within the given time we will re-transmit 36 the request to the server in hopes that the server will respond within 37 time to this request. This number dictates the number of times we will
|
/Zephyr-latest/subsys/bluetooth/audio/ |
D | Kconfig.cap | 16 Enabling this will enable the CAP Acceptor role. This instantiates the 25 Enabling this will allow a CAP acceptor to be a set member. 26 Enabling this will require a manual register of the CAS service. 27 Enabling will take one of the allocated CSIS instances 38 Enabling this will enable the CAP Initiator role. 50 Enabling this will enable the CAP Initiator role.
|
/Zephyr-latest/tests/boards/espressif/wifi/ |
D | Kconfig | 19 It allows you to specify the Wi-Fi SSID that the device will 27 during test scenarios. The device will use this password to authenticate 46 If connection is not successful after all attempts, test will fail. 53 If timeout happens in all attempts, test will fail. 60 If scan doesn't complete within this time, test will fail. 67 If connection is not established within this time, test will fail. 74 If disconnect doesn't complete within this time, test will fail. 81 If no reply is received within this time, test will fail.
|
/Zephyr-latest/drivers/serial/ |
D | Kconfig.xmc4xxx | 24 When this option is enabled, an interrupt will continue to trigger 25 if there is data in the receive fifo. Otherwise, an interrupt will 26 trigger only once on the first received byte. The receive fifo will 27 need to be fully flushed so that the interrupt will trigger again.
|
/Zephyr-latest/samples/bluetooth/bap_broadcast_assistant/ |
D | Kconfig | 10 Name of broadcast source device to select. This will be used as a 12 If empty, the first broadcast source found will be chosen. 19 Name of broadcast sink device to select. This will be used as a 21 If empty, the first broadcast sink found will be chosen.
|
/Zephyr-latest/scripts/dts/ |
D | README.txt | 22 For now, the 'main' copy will continue to be hosted here in the zephyr 23 repository. We will mirror changes into the standalone repository as 26 Code in the zephyr repository which needs these libraries will import 27 devicetree.edtlib from now on, but the code will continue to be found 31 repository will disappear, and a standalone repository will be the
|
/Zephyr-latest/subsys/mgmt/mcumgr/ |
D | Kconfig | 26 This will enable legacy result code response behaviour of having rc 28 mcumgr acts with new behaviour and will only return rc is the result 31 If a command only returns a result code, this will mean that the 32 response will be empty with the new behaviour enabled, as opposed to 33 the old behaviour where the rc field will be present in the response.
|
/Zephyr-latest/drivers/flash/ |
D | Kconfig.rv32m1 | 13 WARNING: This driver will disable the system interrupts for 14 the duration of the flash erase/write operations. This will 16 this is acceptable or not will depend on the use case.
|
D | Kconfig.lpc | 14 WARNING: This driver will disable the system interrupts for 15 the duration of the flash erase/write operations. This will 17 this is acceptable or not will depend on the use case.
|
/Zephyr-latest/lib/posix/options/ |
D | Kconfig.fd_mgmt | 8 Select 'y' here and Zephyr will provide implementations for the POSIX_FD_MGMT Option Group. 23 When selected via Kconfig, Zephyr will provide an alias for fcntl() as _fcntl(). 28 When selected via Kconfig, Zephyr will provide an alias for ftruncate() as _ftruncate(). 33 When selected via Kconfig, Zephyr will provide an alias for lseek() as _lseek().
|
D | Kconfig.device_io | 14 Select 'y' here and Zephyr will provide an implementation of the POSIX_DEVICE_IO Option 29 When selected via Kconfig, Zephyr will provide an alias for close() as _close(). 34 When selected via Kconfig, Zephyr will provide an alias for open() as _open(). 39 When selected via Kconfig, Zephyr will provide an alias for read() as _read(). 44 When selected via Kconfig, Zephyr will provide an alias for write() as _write().
|
/Zephyr-latest/samples/bluetooth/periodic_sync_rsp/ |
D | README.rst | 13 This sample will echo the data received in subevent indications back to the 18 Upon connection it will write to a GATT characteristic 21 Flash this sample to multiple devices and they will be given different 38 another board that will start periodic advertising, which will connect to this
|
/Zephyr-latest/doc/security/ |
D | reporting.rst | 10 vulnerabilities@zephyrproject.org mailing list. These reports will be 12 Each vulnerability will be entered into the Zephyr Project security 13 advisory GitHub_. The original submitter will be granted permission to 21 Issues within this bug tracking system will transition through a 58 response team will analyze the issue, determine a responsible 60 issue to the Assigned state. Part of triage will be to set the 67 link will be added to a comment in the issue, and the issue moved to 73 - Public: The embargo period has ended. The issue will be made 87 Subcommittee. In the general case, this will include: 99 The guideline for embargo will be based on: 1. Severity of the issue, [all …]
|
/Zephyr-latest/tests/cmake/snippets/ |
D | app.overlay | 2 /* This node will be deleted by the `foo` snippet. */ 5 /* This node will be deleted by the `bar` snippet. */
|
/Zephyr-latest/samples/subsys/fs/littlefs/ |
D | README.rst | 26 The partition labeled "storage" will be used for the file system; see 28 compatible littlefs file system its contents will be replaced by an 29 empty file system. You will see diagnostics like this:: 94 It is possible that both the ``zephyr,sdmmc-disk`` and ``zephyr,mmc-disk`` block devices will be 96 point name for the ``littlefs`` file system block device will be determined based on the 100 will be used as the mount point name; 102 :kconfig:option:`CONFIG_DISK_DRIVER_MMC` configuration is defined, ``"SD2"`` will 105 configurations are defined, the mount point name will not be determined, and an appropriate error 106 will appear during the sample build. 111 On this device the file system will be placed in the SOC flash. [all …]
|
/Zephyr-latest/subsys/mgmt/mcumgr/grp/shell_mgmt/ |
D | Kconfig | 21 Enables MCUmgr handlers for shell management. The handler will utilize 26 with this handler and they will not interfere. 27 The MCUMGR_GRP_SHELL_BACKEND_DUMMY_BUF_SIZE will affect how many characters 28 will be returned from command output, if your output gets cut, then 38 # Show dummy shell buffer size here, will show help text of original prompt so 49 disabled, there will be an additional ret field which contains the 50 shell command exit code, and rc will be used for SMP processing
|
/Zephyr-latest/cmake/ |
D | target_toolchain_flags.cmake | 7 # the MD5 will also change (as example toolchain upgrade in same folder) 9 # multiple symlinks pointing to same executable will generate different 11 # ccache will generate unique signatures 13 # * CMAKE_C_COMPILER_VERSION will ensure that even when using the previous 15 # usage and symbolic links, then the upgraded compiler will have new version 18 # Toolchains with the same signature will always support the same set of flags. 27 # Load the compile features file which will provide compile features lists for
|
/Zephyr-latest/soc/espressif/common/ |
D | Kconfig.flash | 20 chips, however will extend detecting time. 28 chips, however will extend detecting time. 39 This adds support for variant chips, however will extend detecting time and image 49 chips, however will extend detecting time. 57 chips, however will extend detecting time. 65 chips, however will extend detecting time. 74 chips, however will extend detecting time. 90 XMC chips will be forbidden to be used, when this option is disabled. 100 or MTDI bootstrapping pin), bootloader will change LDO settings to 119 This will ensure that an exception will be triggered whenever the CPU performs a memory [all …]
|
/Zephyr-latest/subsys/net/ |
D | Kconfig.hostname | 24 This will enable the net_hostname_set() function. NET_HOSTNAME 25 will be used as default hostname. 33 This will set the number of bytes allocateed for the hostname. 38 This will append link address to NET_HOSTNAME to create a unique 46 This will update the unique hostname on link address changes. By
|
/Zephyr-latest/tests/net/lib/mqtt/v3_1_1/mqtt_packet/ |
D | README | 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
|
/Zephyr-latest/doc/ |
D | zephyr.doxyfile.in | 9 # All text after a single hash (#) is considered a comment and will be ignored. 61 # pixels and the maximum width should not exceed 200 pixels. Doxygen will copy 67 # when the HTML document is shown. Doxygen will copy the logo to the output 73 # into which the generated documentation will be written. If a relative path is 74 # entered, it will be relative to the location where Doxygen was started. If 75 # left blank the current directory will be used. 79 # If the CREATE_SUBDIRS tag is set to YES then Doxygen will create up to 4096 81 # and will distribute the generated files over these directories. Enabling this 90 # Controls the number of sub-directories that will be created when 101 # If the ALLOW_UNICODE_NAMES tag is set to YES, Doxygen will allow non-ASCII [all …]
|
/Zephyr-latest/subsys/mgmt/mcumgr/grp/settings_mgmt/ |
D | Kconfig | 20 Selects if the stack or heap will be used for variables that are 27 this will be rejected. 29 Note that stack usage for parameter storage alone will be 38 insufficient heap memory for the allocation then the request will be 47 Maximum length of a key to lookup, this will be the size of the 55 Maximum length of a value to read, this will be the size of the
|
/Zephyr-latest/doc/kernel/ |
D | code-relocation.rst | 8 This feature will allow relocating .text, .rodata, .data, and .bss sections from 14 actually having to modify the code. In simple terms this script will do the job 28 ``prj.conf``, will invoke the script and do the required relocation. 38 section will have some info regarding vector tables and other debug related 39 info. The second section will have the complete text section. This is 41 locations. This is due to the behavior of the linker. The linker will only 89 This will place data and bss inside SRAM2. 103 By default, all relocated functions and variables will be marked with ``KEEP()`` 105 contain unused symbols, then they will not be discarded by the linker, even when 113 The example above will help ensure that any unused code found in the .text [all …]
|
/Zephyr-latest/share/sysbuild/ |
D | Kconfig.v2 | 20 "plank@foo", this option will be "foo". If BOARD is "plank", 21 this option will be the empty string. 27 the Zephyr release that the board configuration will be removed. 28 When set, any build for that board will generate a clearly visible
|
/Zephyr-latest/boards/udoo/udoo_neo_full/ |
D | udoo_neo_full_mcimx6x_m4.dts | 12 * Determines the address and size for code memory which will be applied 17 #define DT_FLASH_ADDR 84000000 /* DT_ADDR will add leading 0x where needed */ 20 * Determines the address and size for data memory which will be applied 25 #define DT_SRAM_ADDR 84080000 /* DT_ADDR will add leading 0x where needed */
|
12345678910>>...66