Home
last modified time | relevance | path

Searched refs:seen (Results 1 – 25 of 57) sorted by relevance

123

/Zephyr-latest/doc/releases/
Drelease-notes-1.9.rst260 * ``ZEP-2258`` - Coverity static scan issues seen
293 * ``ZEP-2343`` - Coverity static scan issues seen
294 * ``ZEP-2344`` - Coverity static scan issues seen
295 * ``ZEP-2345`` - Coverity static scan issues seen
298 * ``ZEP-2355`` - Coverity static scan issues seen
339 * ``ZEP-2465`` - Static code scan (coverity) issues seen
340 * ``ZEP-2467`` - Static code scan (coverity) issues seen
341 * ``ZEP-2468`` - Static code scan (coverity) issues seen
342 * ``ZEP-2469`` - Static code scan (coverity) issues seen
343 * ``ZEP-2474`` - Static code scan (coverity) issues seen
[all …]
Drelease-notes-1.10.rst337 * :github:`3897` - Static code scan (coverity) issues seen
354 * :github:`4030` - Coverity issue seen with CID: 175366 , in file: /subsys/bluetooth/host/smp.c
355 * :github:`4031` - Coverity issue seen with CID: 175365 , in file: /subsys/bluetooth/controller/hci…
356 * :github:`4032` - Coverity issue seen with CID: 175364 , in file: /subsys/bluetooth/host/mesh/prox…
357 * :github:`4033` - Coverity issue seen with CID: 175363 , in file: /subsys/bluetooth/host/smp.c
358 * :github:`4034` - Coverity issue seen with CID: 175362 , in file: /subsys/bluetooth/host/smp.c
359 * :github:`4035` - Coverity issue seen with CID: 175361 , in file: /samples/bluetooth/eddystone/src…
360 * :github:`4036` - Coverity issue seen with CID: 175360 , in file: /subsys/bluetooth/host/mesh/prov…
361 * :github:`4037` - Coverity issue seen with CID: 175359 , in file: /subsys/bluetooth/host/hci_core.c
362 * :github:`4038` - Coverity issue seen with CID: 175358 , in file: /subsys/bluetooth/host/hci_core.c
[all …]
/Zephyr-latest/tests/subsys/rtio/rtio_api/src/
Dtest_rtio_api.c200 bool seen[4] = { 0 }; in test_rtio_multiple_chains_() local
217 seen[(uintptr_t)cqe->userdata] = true; in test_rtio_multiple_chains_()
218 if (seen[1]) { in test_rtio_multiple_chains_()
219 zassert_true(seen[0], "Should see 0 before 1"); in test_rtio_multiple_chains_()
221 if (seen[3]) { in test_rtio_multiple_chains_()
222 zassert_true(seen[2], "Should see 2 before 3"); in test_rtio_multiple_chains_()
554 bool seen[2] = { 0 }; in test_rtio_transaction_() local
597 seen[idx] = true; in test_rtio_transaction_()
601 zassert_true(seen[0], "Should have seen transaction 0"); in test_rtio_transaction_()
602 zassert_true(seen[1], "Should have seen transaction 1"); in test_rtio_transaction_()
/Zephyr-latest/drivers/usb/bc12/
DKconfig.pi3usb920137 This is a workaround for a glitch seen on the USB data lines when
/Zephyr-latest/samples/sensor/tmp116/
DREADME.rst48 The output can be seen via a terminal emulator (e.g. minicom). Connect the board with a USB cable
/Zephyr-latest/subsys/logging/
DKconfig.misc34 Depending on the architecture code size reduction is from 0-40% (highest seen on
47 (seen on arm_cortex_m and x86) were using unrealistic amount of stack
/Zephyr-latest/share/zephyr-package/cmake/
Dzephyr_package_search.cmake6 # Relative directory of workspace project dir as seen from Zephyr package file
9 # Relative directory of Zephyr dir as seen from Zephyr package file
/Zephyr-latest/doc/services/storage/stream/
Dstream_flash.rst18 in faster response times seen from the application.
/Zephyr-latest/drivers/wifi/nrf_wifi/
DCMakeLists.txt71 # but as its rare and not seen in most cases, we can disable it.
/Zephyr-latest/doc/security/
Dhardening-tool.rst10 At a high-level, hardening a Zephyr application can be seen as a two-fold process:
/Zephyr-latest/samples/subsys/llext/shell_loader/
DREADME.rst34 which can be seen with llext help
139 This extension can then be seen in the list of loaded extensions (``list``), its symbols printed
/Zephyr-latest/samples/net/sockets/echo/
DREADME.rst73 As can be seen, the behavior of the application is the same as the Zephyr
/Zephyr-latest/samples/net/sockets/echo_async_select/
DREADME.rst77 As can be seen, the behavior of the application is the same as the Zephyr
/Zephyr-latest/samples/net/sockets/socketpair/
DREADME.rst92 As can be seen, the behavior of the application is approximately the same as
/Zephyr-latest/doc/services/portability/posix/overview/
Dindex.rst28 embedded applications, as can be seen in Zephyr, AWS:FreeRTOS, TI-RTOS, and NuttX.
46 same binary artifact. From that perspective, Zephyr apps can be seen as running in the context of
/Zephyr-latest/samples/net/sockets/dumb_http_server/
DREADME.rst82 As can be seen, the behavior of the application is the same as the Zephyr
/Zephyr-latest/samples/net/sockets/echo_async/
DREADME.rst85 As can be seen, the behavior of the application is the same as the Zephyr
/Zephyr-latest/doc/connectivity/bluetooth/
Dfeatures.rst15 grown to be mature and feature-rich, as can be seen in the section below.
/Zephyr-latest/samples/net/sockets/http_get/
DREADME.rst97 As can be seen, the behavior of the application is the same as the Zephyr
/Zephyr-latest/doc/hardware/cache/
Dguide.rst21 in general ensures that memory will be seen in a coherent state from multiple
35 There are multiple approaches to ensuring that the data seen by the processor
/Zephyr-latest/samples/modules/chre/
DREADME.rst9 Android's context hub enables the use of nanoapps. A single nanoapp has 3 entry points seen in
/Zephyr-latest/boards/others/stm32_min_dev/doc/
Dindex.rst35 The pinout diagram of STM32 Minimum Development Blue Pill board can be seen
/Zephyr-latest/boards/arm/fvp_baser_aemv8r/doc/
Ddebug-with-arm-ds.rst52 Click ``Finish`` and the new configuration database can be seen in ``Project Explorer``:
/Zephyr-latest/subsys/net/ip/
DKconfig998 timing information can then be seen in network interface statistics
1009 The extra statistics can be seen in net-shell using "net stats"
1021 information can then be seen in network interface statistics in
1034 The extra statistics can be seen in net-shell using "net stats"
1043 The extra statistics can be seen in net-shell using "net mem"
/Zephyr-latest/subsys/net/l2/ethernet/gptp/
DKconfig212 can be seen in net-shell if needed.

123