Home
last modified time | relevance | path

Searched refs:allocate (Results 76 – 94 of 94) sorted by relevance

1234

/Zephyr-latest/doc/releases/
Dmigration-guide-3.5.rst214 set in the board DTS as a way to configure the amount of structures the driver will allocate.
Dmigration-guide-3.6.rst474 application should register the `alloc_seg` channel callback and allocate from the same pool as
Drelease-notes-3.1.rst987 * mcumgr will now only return ``MGMT_ERR_ENOMEM`` when it fails to allocate
1172 - :github:`37731` - Bluetooth: hci samples: Unable to allocate command buffer
1661 * :github:`43718` - Bluetooth: bt_conn: Unable to allocate buffer within timeout
Drelease-notes-3.3.rst307 the minimum fragment length to allocate, so that they work correctly also in
2609 - :github:`37731` - Bluetooth: hci samples: Unable to allocate command buffer
2703 - :github:`53006` - Hawbkit with b_l4s5i_iot01a - wifi_eswifi: Cannot allocate rx packet
3407 * :github:`51261` - drivers: ieee802154: Drivers allocate RX packets from the TX pool
Drelease-notes-3.4.rst145 on the stack. Applications that allocate a sensor trigger on the stack need
Drelease-notes-3.6.rst1169 * Added support to allocate and free stacks up to 8 MB with pthread_attr_t.
Drelease-notes-2.2.rst614 * GAP: Pre-allocate connection objects for connectable advertising and
Drelease-notes-3.2.rst1668 - :github:`37731` - Bluetooth: hci samples: Unable to allocate command buffer
2527 * :github:`43718` - Bluetooth: bt_conn: Unable to allocate buffer within timeout
Drelease-notes-2.3.rst934 * :github:`24727` - Unable allocate buffer to send mesh message
Drelease-notes-2.0.rst535 * :github:`18705` - SMP fails to allocate buffer and pairing times out
Drelease-notes-2.5.rst1561 * :github:`29148` - MPU: twr_ke18f: many kernel application fails when allocate dynamic MPU region
/Zephyr-latest/doc/kernel/services/threads/
Dindex.rst37 allocate CPU time to the thread. (See :ref:`scheduling_v2`.)
/Zephyr-latest/doc/connectivity/networking/api/
Dlwm2m.rst506 Application needs to allocate an array of :c:struct:`lwm2m_time_series_elem` structures and then
/Zephyr-latest/doc/connectivity/usb/device/
Dusb_device.rst569 Steering Committee, may allocate other USB Product IDs based on well-motivated
/Zephyr-latest/drivers/ethernet/
Deth_sam_gmac.c132 #error Not enough RX buffers to allocate descriptors for each HW queue
/Zephyr-latest/doc/services/storage/zms/
Dzms.rst381 - Divide IDs into namespaces and allocate IDs on demand from application to handle collisions
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst478 large to allocate on the stack. In this scenario, it may be necessary to draw
/Zephyr-latest/doc/services/logging/
Dindex.rst454 It may happen that the frontend cannot allocate a message. This happens if the
/Zephyr-latest/kernel/
DKconfig268 Pre-allocate a fixed number of thread objects and

1234