Home
last modified time | relevance | path

Searched refs:very (Results 126 – 150 of 165) sorted by relevance

1234567

/Zephyr-latest/doc/connectivity/networking/api/
Dnet_pkt.rst56 through or through which it was received. As this is a very common
/Zephyr-latest/doc/security/
Dsecure-coding.rst9 from the world, and not very vulnerable, just because of the
Dvulnerabilities.rst704 * Asking for very large size values leads to internal integer wrap-around.
705 * Integer wrap-around leads to successful allocation of very small memory.
Dsecurity-overview.rst67 SHOULD NOT be done may be very subtle. Document authors should take the
/Zephyr-latest/doc/build/dts/
Dtroubleshooting.rst295 Compiler messages for devicetree errors can sometimes be very long. This
Dapi-usage.rst289 This is currently not very well documented, and you'll need to read the
/Zephyr-latest/subsys/debug/
DKconfig213 with stack overflows, knowledge that this is happening is very
/Zephyr-latest/doc/connectivity/bluetooth/shell/host/
Dgap.rst54 Or if you want to look for devices at a very close range:
/Zephyr-latest/doc/connectivity/networking/conn_mgr/
Dmain.rst10 This allows an application to potentially support several very different connectivity technologies …
/Zephyr-latest/modules/mbedtls/
DKconfig.tls-generic582 …Users can enable it in case of very memory-constrained devices, but be aware that the p256-m inter…
/Zephyr-latest/subsys/shell/backends/
DKconfig.backends117 CPU load is high and there is very high shell thread latency.
/Zephyr-latest/boards/intel/adsp/doc/
Dchromebooks_adsp.rst251 device. Note that this filesystem has very limited space (it's
/Zephyr-latest/subsys/bluetooth/mesh/
DKconfig439 this value to a very low number can cause unnecessary network traffic.
440 Setting this value to a very large number can impact the processing time
1847 100th increment. If the node sends messages very frequently a
/Zephyr-latest/doc/contribute/documentation/
Dguidelines.rst574 example how this is done at the beginning of this very document).
931 very file can be done using the :rst:role:`zephyr_file` role, like this::
/Zephyr-latest/doc/kernel/usermode/
Dmemory_domain.rst58 of this should be treated as a serious error. However it's still very useful to
/Zephyr-latest/doc/releases/
Dmigration-guide-3.5.rst28 * :c:macro:`CONTAINER_OF` now performs type checking, this was very commonly
Drelease-notes-3.6.rst424 adding a GNSS modem is very efficient due to the reuse of subsystems.
1103 very helpful in diagnosing issues when using Picolibc as those are often caused by enabling TLS
Drelease-notes-3.1.rst304 * The k_timer handler can now correct itself for lost time due to very
1751 * :github:`43159` - hal: stm32: ltdc pins should be very-high-speed
1764 * :github:`43081` - [Slack] Slack invite works only on very few mail addresses - this should be cha…
/Zephyr-latest/doc/kernel/services/threads/
Dindex.rst304 very high priority threads and should not be used as such.
/Zephyr-latest/doc/services/tracing/
Dindex.rst233 This allows for recording very long traces. To configure Zephyr for RTT streaming to Tracealyzer,
/Zephyr-latest/doc/services/shell/
Dindex.rst74 This will give the telnet client access to a very limited set of supported commands but
/Zephyr-latest/
DCMakeLists.txt1827 # Those files can be very large in some cases, delete them as we do not need them.
2271 # Done at the very end, so any other system includes which may
/Zephyr-latest/doc/hardware/arch/
Darm_cortex_m.rst190 It is, therefore, considered as a lightweight but very efficient stack overflow
/Zephyr-latest/doc/_static/css/
Dcustom.css762 /* This fixes the class reference titles' display with very long class names */
/Zephyr-latest/doc/build/kconfig/
Dtips.rst167 well. This is very often overlooked in practice, even for the simplest case

1234567