You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If zephyr compiled with CONFIG_BT_HCI_ACL_FLOW_CONTROL=y is used with a controller which does not support hci acl flow control, it should not use acl_in_pool. The function bt_buf_get_rx() misses checking the flow control capability of controller and allocates from acl_in_pool for all types which are other than BT_BUF_EVT.
The text was updated successfully, but these errors were encountered:
See my comment in the pull request. I'm failing to understand how the current behavior is "bad". Btw, the general assumption is that an application writer fine-tunes the configuration for the hardware that is being targeted, so in this case you simply wouldn't enable CONFIG_BT_HCI_ACL_FLOW_CONTROL since you know your hardware doesn't support it. Don't we also have board-specific defaults which could set this to "n" for your board?
If zephyr compiled with CONFIG_BT_HCI_ACL_FLOW_CONTROL=y is used with a controller which does not support hci acl flow control, it should not use acl_in_pool. The function bt_buf_get_rx() misses checking the flow control capability of controller and allocates from acl_in_pool for all types which are other than BT_BUF_EVT.
The text was updated successfully, but these errors were encountered: