diff options
| author | Stephan Gerhold <stephan.gerhold@kernkonzept.com> | 2022-08-15 14:07:39 +0200 |
|---|---|---|
| committer | Stephan Gerhold <stephan.gerhold@kernkonzept.com> | 2022-08-18 18:14:31 +0200 |
| commit | 3df2c4f03c2eacc90205a913c234a04d60f24696 (patch) | |
| tree | 1eda87e1ef24f8b473af0f24c759bbed615a90ad /src/mm-port-qmi.h | |
| parent | bc1cecbfc40bbac48beaf9bfe20f1403ebdbb959 (diff) | |
mm-bearer-qmi: allocate separate WDS client for each endpoint
Multiplexing currently does not work correctly for BAM-DMUX because
ModemManager reuses the same WDS client for all data points. A second
bearer can be created but it effectively disables the first one.
Fix this similar to the existing checks for the mux-id by including the
endpoint type and number in the QMI client flags.
Diffstat (limited to 'src/mm-port-qmi.h')
| -rw-r--r-- | src/mm-port-qmi.h | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/src/mm-port-qmi.h b/src/mm-port-qmi.h index c177925c..7b434cdb 100644 --- a/src/mm-port-qmi.h +++ b/src/mm-port-qmi.h @@ -100,11 +100,6 @@ typedef enum { MM_PORT_QMI_FLAG_WDS_IPV6 = 2, } MMPortQmiFlag; -/* When using the WDS service, we may not only want to have explicit different - * clients for IPv4 or IPv6, but also for different mux ids as well, so that - * different bearer objects never attempt to use the same WDS clients. */ -#define MM_PORT_QMI_FLAG_WITH_MUX_ID(flag, mux_id) ((mux_id << 8) | (flag & 0xFF)) - void mm_port_qmi_allocate_client (MMPortQmi *self, QmiService service, guint flag, |