Home
last modified time | relevance | path

Searched refs:could (Results 301 – 320 of 320) sorted by relevance

1...<<111213

/Zephyr-latest/doc/releases/
Drelease-notes-3.7.rst294 where racing ISRs on SMP systems could become stuck spinning to
889 :kconfig:option:`CONFIG_I2C_STM32_V2_TIMING` could be disabled, bus timings configured
1706 * Fix case when logging strings could be stripped from the binary when dictionary based logging
Drelease-notes-3.0.rst1065 * :github:`41077` - console: gsm_mux: could not send more than 128 bytes of data on dlci
1198 * :github:`39900` - usb bug :USB device descriptor could not be obtained on windows10
Drelease-notes-2.2.rst254 * Fix an issue where callee-saved registers could be unnecessarily
261 * Fix an issue where reserved memory could be overwritten when loading the
Drelease-notes-1.10.rst173 * Note added to all released doc pages mentioning more current content could
Drelease-notes-2.6.rst271 * Fixed an issue where GATT requests could deadlock the RX thread.
272 * Fixed an issue where a fixed passkey that was previously set could not be
276 * Changed the pairing procedure to fail early if the remote device could not
278 * Fixed an issue where GATT notifications and Writes Without Response could
Drelease-notes-3.1.rst350 * Fixed a bug that could return directly into a thread context from a
653 * Fixed a bug which could cause a socket descriptor leak, in case
706 This could led to TX buffer starvation when TCP entered retransmission mode.
Drelease-notes-2.0.rst80 scheduled by kernel. On very loaded systems it could cause swap errors.
1202 * :github:`15714` - samples/bluetooth/peripheral: could not connect with disco_l475_iot1 board
Drelease-notes-2.5.rst1633 * :github:`28867` - ARM Cortex-M4: Semaphores could not be used in ISRs with priority 0?
1818 * :github:`25832` - [test][kernel][lpcxpresso55s69_ns] kernel cases meet ESF could not be retrieved…
Drelease-notes-2.4.rst694 throughput could not reach the expected values.
1570 * :github:`25311` - samples:frdmkw64f:bluetooth/peripheral_hr| peripheral_ht: could not get ADC dev…
Drelease-notes-1.14.rst1619 * :github:`13034` - samples/bluetooth/peripheral_hr: could not connect with reel board
2171 * :github:`9432` - Overriding 'LOG_LEVEL' could crash the firmware
Drelease-notes-2.3.rst792 * :github:`25698` - IPv6 prefix could be added multiple times to prefix timer list
/Zephyr-latest/
DKconfig.zephyr881 It can also be a pattern with wildcards, such as "*bss", which could
/Zephyr-latest/subsys/bluetooth/host/
DKconfig593 This would enable cases where an attacker could copy the peer device
/Zephyr-latest/doc/contribute/
Dguidelines.rst960 APIs due to specialized accelerators in a particular SoC family, one could
/Zephyr-latest/doc/contribute/documentation/
Dguidelines.rst359 If asterisks or backquotes appear in running text and could be confused with
/Zephyr-latest/kernel/
DKconfig451 initialization. Such boot-time optimization could be used for
/Zephyr-latest/doc/
Dzephyr.doxyfile.in48 # could be handy for archiving the generated documentation or if some version
937 # be replaced by the version of the file (if it could be obtained via
1746 # Since the tree basically has the same information as the tab index, you could
/Zephyr-latest/doc/develop/
Dmodules.rst595 A real life example for ``mbedTLS`` module could look like this:
/Zephyr-latest/doc/develop/test/
Dtwister.rst585 interface would enable other interesting uses. For example, this could enable
/Zephyr-latest/samples/modules/tflite-micro/hello_world/train/
Dtrain_hello_world_model.ipynb2959 … straight when `x` is between 4.2 and 5.2. If we wanted to go further, we could try further increa…

1...<<111213