aboutsummaryrefslogtreecommitdiff
path: root/docs/reference
diff options
context:
space:
mode:
authorStephan Gerhold <stephan.gerhold@kernkonzept.com>2022-08-11 17:53:00 +0200
committerStephan Gerhold <stephan.gerhold@kernkonzept.com>2022-08-18 18:12:49 +0200
commitbc1cecbfc40bbac48beaf9bfe20f1403ebdbb959 (patch)
treed1ad606b69cbc1f8817af6832d8d286be7851daa /docs/reference
parent2b83e274742039432de81f663c34383c238d0314 (diff)
broadband-modem-qmi: choose endpoint number based on data port
At the moment the endpoint type/number is chosen based on the QMI control port. The assumption is that multiplexing is implemented using an additional protocol layer (e.g. QMAP) or that each network interface has its own QMI control port. This is not necessarily the case for BAM-DMUX. To use the built-in multiplexing the WDS client must be bound to the correct data port. This works already for older firmware versions using "Bind Data Port" (SIO port numbers), but not for newer ones using "Bind Mux Data Port" (endpoint type/interface numbers). Make it work for newer firmware versions as well by choosing the endpoint type/number based on the data port similar to the existing implementation for SIO port numbers. Note: The correct endpoint interface number is currently only used for the steps in mm-bearer-qmi. Ideally more refactoring should be done in mm-port-qmi to call WDA Set Data Format for each of the endpoints. In practice it usually works fine without because the data format is set correctly by default.
Diffstat (limited to 'docs/reference')
0 files changed, 0 insertions, 0 deletions