Searched refs:being (Results 276 – 300 of 345) sorted by relevance
1...<<11121314
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-4.1.rst | 357 :kconfig:option:`CONFIG_NET_IPV4_DEFAULT_NETMASK` option instead of being left
|
| D | release-notes-3.2.rst | 201 of :c:enumerator:`CAN_STATE_STOPPED` before being able to transmit and receive CAN frames.
749 * Enhanced the LPS22HH driver to support being on an I3C bus.
1437 * Issue with :c:func:`img_mgmt_dfu_stopped` being wrongly called on success
1767 - :github:`50196` - LSM6DSO interrupt handler not being called
1797 - :github:`50776` - CAN Drivers allow sending FD frames without device being set to FD mode
1823 * :github:`50654` - Some files are being ALWAYS built, without them being used
2001 * :github:`49410` - Bluetooth: Scan responses with info about periodic adv. sometimes stops being r…
2246 * :github:`47426` - ZTEST_USER tests being skipped on systems without userspace support
|
| D | release-notes-3.0.rst | 397 * Fixed DTM mode not being reset correctly with the HCI Reset command
801 * Support all syscalls being traced using the python syscall generator to
912 * :github:`42358` - net: lwm2m: client context accessed after being invalidated in lwm2m_rd_client_…
972 * :github:`41942` - k_delayable_work being used as k_work in work's handler
|
| D | release-notes-2.1.rst | 517 * :github:`20800` - Ready thread is not swapped in after being woken up in IRQ
598 * :github:`20299` - bluetooth: host: Connection not being unreferenced when using CCC match callback
738 * :github:`19284` - Service Changed indication not being sent in some cases
|
| /Zephyr-latest/doc/hardware/peripherals/can/ |
| D | controller.rst | 68 Nodes monitor the bus and notice when their transmission is being overridden and
|
| /Zephyr-latest/doc/services/debugging/ |
| D | coredump.rst | 321 the target and is only being parsed by the target parser.
|
| /Zephyr-latest/doc/connectivity/usb/device_next/ |
| D | usb_device.rst | 279 Filling the TX FIFO does not mean that data is being sent to the host. And
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | http_server.rst | 126 HTTPS services rely on TLS credentials being registered in the system.
|
| D | net_pkt.rst | 170 latter being the preferred way.
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 143 because they end up being compiled in a surprisingly high number of other
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | i3c.rst | 57 If this is being used, this struct needs to be initialized by calling
|
| /Zephyr-latest/boards/arm/v2m_musca_s1/doc/ |
| D | index.rst | 326 format before being flashed to a V2M Musca-S1. An optional bootloader can also
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net_config_guide.rst | 58 If TCP is being used, then these values need to be higher because we can queue the
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 31 build process makes a number of assumptions about how TF-M is being used, and
|
| /Zephyr-latest/subsys/debug/ |
| D | Kconfig | 243 purpose. For instance, in case of STDOUT_CONSOLE being set it will
|
| /Zephyr-latest/subsys/bluetooth/controller/ |
| D | Kconfig.ll_sw_split | 616 When enabled, this could result in an SDU being fragmented into
1099 This will prolong the connection event to from being closed in cases
1332 been processed. The rationale for default behavior being that under
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 712 * If this is built normally without ``FILE_SUFFIX`` being defined for ``native_sim`` then
715 * If this is build normally without ``FILE_SUFFIX`` being defined for ``qemu_cortex_m3`` then
1047 support being unavailable, consult :ref:`your board's documentation <boards>`
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 118 * When performing a context switch, restore the context being context
235 when an object being operated on is unavailable, and some thread
366 exception 1 is IRQ1, and device IRQs start at 16), ARM has IRQ0 being
|
| /Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
| D | mcp.rst | 176 being too long to fit in the ATT packet. Increasing the ATT MTU may
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | main.rst | 209 Many network interfaces require a network association procedure to be completed before being usable.
|
| /Zephyr-latest/doc/develop/tools/ |
| D | coccinelle.rst | 123 description of the problem being checked by the semantic patch, and
|
| /Zephyr-latest/doc/services/pm/ |
| D | device.rst | 8 save energy when they are not being used. This feature can be enabled by
|
| /Zephyr-latest/doc/safety/ |
| D | safety_overview.rst | 266 being certified. If the certification body approves everything at this stage and the safety
|
| /Zephyr-latest/subsys/shell/backends/ |
| D | Kconfig.backends | 14 # Workaround for not being able to have commas in macro arguments
|
| /Zephyr-latest/arch/ |
| D | Kconfig | 211 # Workaround for not being able to have commas in macro arguments
232 # Workaround for not being able to have commas in macro arguments
|
1...<<11121314
