Searched refs:very (Results 151 – 165 of 165) sorted by relevance
1234567
1173 When the data is very application specific (e.g. advertising data),
80 scheduled by kernel. On very loaded systems it could cause swap errors.1361 * :github:`13610` - kernel: Non-deterministic and very high ISR latencies
533 * :github:`8378` - subsys: settings: Idea for a very simple settings system
1153 * :github:`27503` - testcases under zephyr/tests/application_development take a very long time to d…1816 * :github:`15968` - rom_report very imprecise
1157 * :github:`38463` - check_compliance gives very many Kconfig warnings1408 * :github:`37536` - _pm_devices() skips the very first device in the list and suspend() is not call…
1503 by Linux's very successful io_uring.2684 * :github:`12191` - Nested interrupt test has very poor coverage
1517 * :github:`13610` - kernel: Non-deterministic and very high ISR latencies2224 * :github:`7441` - newlib support in zephyr is untested and very broken
932 * :github:`24744` - k_thread_join() taking a very long time on qemu_cortex_m3
2812 - :github:`54695` - usb mass storage on mimxrt595_evk_cm33 mount very slow3152 * :github:`52872` - Logging to USB CDC ACM limited to very low rate
1354 * :github:`30098` - > very few are even tested with CONFIG_NO_OPTIMIZATIONS. What is the general co…
1273 * :github:`35046` - Tracing shows k_busy_wait() being executed very often on nRF platforms
20 Licensing is very important to open source projects. It helps ensure the
66 # As a very high-level introduction here are two call graphs that are1191 # While there are a number of reasons why this race seems both very
1635 …of the model's predictions are at least 30% off. A 30% error means we are very far from accurately…1697 …s it clear that our network has learned to approximate the sine function in a very limited way.\n",
727 # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
