[mynewt-nimble] 01/02: nimble/transport: Use max ACL data size for RAM transport

[an...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

andk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mynewt-nimble.git

commit 815d890d537cd60b50b2797ee56dfc5467e4b4c5
Author: Andrzej Kaczmarek <an...@codecoup.pl>
AuthorDate: Thu Oct 14 15:44:30 2021 +0200

    nimble/transport: Use max ACL data size for RAM transport
    
    Since in RAM transport ACL data are passed simply as an mbuf pointer
    between host and controller we can use max ACL data size to avoid data
    fragmentation over HCI. This actually saves some RAM since we do not
    need extra buffers for fragmented HCI ACL data.
---
 nimble/transport/ram/syscfg.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/nimble/transport/ram/syscfg.yml b/nimble/transport/ram/syscfg.yml
index 3b822fc..cbb5716 100644
--- a/nimble/transport/ram/syscfg.yml
+++ b/nimble/transport/ram/syscfg.yml
@@ -37,7 +37,7 @@ syscfg.defs:
         description: >
             This is the maximum size of the data portion of HCI ACL data
             packets. It does not include the HCI data header (of 4 bytes).
-        value: 255
+        value: 65535
 
     BLE_TRANS_RAM_SYSINIT_STAGE:
         description: >