Searched refs:could (Results 276 – 300 of 320) sorted by relevance
1...<<111213
| /Zephyr-4.1.0/boards/intel/adsp/doc/ |
| D | chromebooks_adsp.rst | 113 kernel out, and that we could probably have just edited the command
|
| /Zephyr-4.1.0/doc/safety/ |
| D | safety_overview.rst | 299 so that the bug fix or change could also be integrated into the auditable branch. This
|
| /Zephyr-4.1.0/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_0.rst | 543 that the SMP client could receive information that the command has been
|
| /Zephyr-4.1.0/doc/releases/ |
| D | release-notes-1.6.rst | 364 * ``ZEP-1345`` - cpu context save and restore could corrupt stack
|
| D | migration-guide-3.5.rst | 264 :kconfig:option:`CONFIG_PM`. Before this change all platforms could enable
|
| D | release-notes-3.2.rst | 847 * Fixed a bug, where only one packet could be queued on a pending ARP
912 You could then use something like the following to retrieve a device
929 misconfigured device drivers could not easily be distinguished from device
1395 thread state changed it could give a falsely short process list has been
1424 caused a deadlock if buffers could not be allocated.
1494 ``PTHREAD_TERMINATED`` could be reused. However, ``pthread_join()`` sets
|
| D | release-notes-4.0.rst | 572 * Driver can now be configured to use a preemptive RX thread priority, which could be useful
975 * Fixed a bug where system workqueue could be blocked indefinitely by DHCPv4 client.
979 * Fixed a bug where system workqueue could be blocked indefinitely by DHCPv6 client.
|
| D | release-notes-1.12.rst | 31 requested buffer. Use of that buffer could result in writes to
539 * :github:`6948` - Kconfig choice symbols could not be assigned in Kconfig.* files
|
| D | release-notes-3.4.rst | 1206 * Fixed implicit type conversion when parsing length field, which could lead
1254 called with ``FS_MOUNT_FLAG_NO_FORMAT`` and the designated LittleFS area could not be
|
| D | release-notes-1.11.rst | 357 * :github:`5448` - STM32: Entropy test could not build
|
| D | release-notes-3.3.rst | 327 could attempt to run a thread before the pending thread had finished
1145 context could be released prematurely.
2132 could have caused a stack overflow has been fixed.
2133 * A MCUmgr issue with Bluetooth transport that could cause a deadlock of the
2136 * A MCUmgr img_mgmt bug whereby the state of an image upload could persist
2399 but could also occur with UART) whereby the default shell receive ring
|
| /Zephyr-4.1.0/boards/espressif/esp_wrover_kit/doc/ |
| D | index.rst | 469 The board could be loaded using the single binary image, without 2nd stage bootloader.
|
| /Zephyr-4.1.0/doc/connectivity/bluetooth/api/audio/ |
| D | bluetooth-le-audio-arch.rst | 1054 A telephone bearer could be any application on a device that can handle (telephone) calls,
1100 A media player on a device could be anything that plays media,
|
| /Zephyr-4.1.0/doc/services/zbus/ |
| D | index.rst | 130 channels) the module needs to work. That indicates zbus could improve the module reuse.
813 defined the ``user_data`` to have the 32 bits integer. This code could be added to the listener code
|
| /Zephyr-4.1.0/doc/hardware/porting/ |
| D | board_porting.rst | 803 Similar for ``letter`` where revision ``A``, ``D``, and ``F`` could be defined
852 Using the ``plank`` board from previous sections, then we could have the following
|
| /Zephyr-4.1.0/doc/hardware/pinctrl/ |
| D | index.rst | 121 Note that other standard states could be introduced in the future.
|
| /Zephyr-4.1.0/doc/kernel/usermode/ |
| D | memory_domain.rst | 35 is accessible to user mode. This could be further sub-divided into a
|
| /Zephyr-4.1.0/boards/espressif/esp32_ethernet_kit/doc/ |
| D | index.rst | 438 The board could be loaded using the single binary image, without 2nd stage bootloader.
|
| /Zephyr-4.1.0/doc/security/ |
| D | sensor-threat.rst | 100 and the generation of tokens with invalid times. It could be
|
| /Zephyr-4.1.0/doc/kernel/services/smp/ |
| D | smp.rst | 298 Similarly, where on a uniprocessor system Zephyr could simply create a
|
| /Zephyr-4.1.0/doc/develop/west/ |
| D | manifest.rst | 658 Since ``group-filter`` is a YAML list, you could have written this fragment
2160 [-foo]`` could be written more simply as ``[-foo]``, for the reasons given
2161 above. As another example, ``[-foo] + [+foo]`` could be written as the empty
|
| /Zephyr-4.1.0/doc/develop/application/ |
| D | index.rst | 639 application directory. For example, C++ support could be enabled with this
1066 For example, you could set ``BOARD`` to:
|
| /Zephyr-4.1.0/doc/build/dts/ |
| D | bindings-syntax.rst | 413 You could then use the property in a devicetree like this:
|
| /Zephyr-4.1.0/scripts/ |
| D | spelling.txt | 434 cound||could
|
| /Zephyr-4.1.0/subsys/bluetooth/controller/ |
| D | Kconfig | 191 A Controller implementation could also provide custom bare-metal
|
1...<<111213
