diff options
| author | Aleksander Morgado <aleksandermj@chromium.org> | 2023-02-17 14:18:16 +0000 |
|---|---|---|
| committer | Aleksander Morgado <aleksandermj@chromium.org> | 2023-02-20 11:07:38 +0000 |
| commit | 6d1f4aee305a6ebeae7bec8b745de33d5368371d (patch) | |
| tree | b608fed991d2b5feae23d83e2f7e94dc1288029d /src/mm-broadband-modem-mbim.h | |
| parent | 278678d8ed818a778377dcb57f5611b04c631450 (diff) | |
broadband-modem-mbim: limit the use of context types defined in MBIMEx
The Tethering context type UUID was defined by Microsoft in its
extensions as `5e4e0601-48dc-4e2b-acb8-08b4016bbaac` (along with
others like Admin, Xcap, App and EmergencyCalling), see
https://learn.microsoft.com/en-us/windows-hardware/drivers/network/mb-provisioned-context-operations.
These UUIDs are expected to be usable only if the modem supports
`MBIM_CID_MS_PROVISIONED_CONTEXT_V2` (CID=1) in the Basic Connect
Extensions service (3d01dcc5-fef5-4d05-0d3abef7058e9aaf).
If the modem doesn't support these, we should try to fallback to a
more generic APN type automatically, e.g. "Internet", which was
defined in MBIM 1.0 and should always be supported.
There should be no problem in a modem to have 2 separate PDN
connections with the same context type.
Diffstat (limited to 'src/mm-broadband-modem-mbim.h')
| -rw-r--r-- | src/mm-broadband-modem-mbim.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/mm-broadband-modem-mbim.h b/src/mm-broadband-modem-mbim.h index e1174540..c6c7bae9 100644 --- a/src/mm-broadband-modem-mbim.h +++ b/src/mm-broadband-modem-mbim.h @@ -71,4 +71,6 @@ void mm_broadband_modem_mbim_get_speeds (MMBroadbandModemMbim *self, guint64 *uplink_speed, guint64 *downlink_speed); +gboolean mm_broadband_modem_mbim_is_context_type_ext_supported (MMBroadbandModemMbim *self); + #endif /* MM_BROADBAND_MODEM_MBIM_H */ |