[roll] Roll fuchsia [bt][rfcomm] Make max_packet_size DLC specific The max packet size is the largest payload that can fit in a single user data frame on the RFCOMM channel. Currently, it is negotiated as a session-wide parameter and therefore the same across all DLCs that are established. RFCOMM 5.5.3 notes that this parameter can be optionally configured per-DLC. Update the SessionMultiplexer to support negotiating the max_packet_size for each DLC, before it is established. The credit flow control mode continues to be a session-wide parameter that can only be negotiated before any DLCs are esablished. While here, add more tests to cover any edge cases in re-negotiating parameters after establishment. Original-Bug: 460778521 Test: fx test bt-rfcomm-tests Test: Manual, fx ota, verify RFCOMM channels can be connected Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1423394 Original-Revision: 01b40662440de8261c6356fbeaaf6b956a58896b GitOrigin-RevId: 11838c59be5325ec0d66e37e3c69c4b3311be94e Change-Id: I02356b29d515ee86f7ab75ec03a2b11e731cd2bb
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.