api,modem: new 'MaxActiveMultiplexedBearers' property
In addition to the amount of bearers a user may connect without multiplexing enabled (the default until now), we now also expose the maximum number of bearers a user may connect after enabling multiplexing over one single network interface (if supported). The method responsible for creating the MMBearerList is now also subclassable, so that implementations supporting multiplexing can provide their own version with their own thresholds.
This commit is contained in:
@@ -162,6 +162,7 @@ mm_modem_peek_unlock_retries
|
||||
mm_modem_get_unlock_retries
|
||||
mm_modem_get_max_bearers
|
||||
mm_modem_get_max_active_bearers
|
||||
mm_modem_get_max_active_multiplexed_bearers
|
||||
mm_modem_get_bearer_paths
|
||||
mm_modem_dup_bearer_paths
|
||||
mm_modem_get_own_numbers
|
||||
@@ -2105,6 +2106,7 @@ mm_gdbus_modem_dup_equipment_identifier
|
||||
mm_gdbus_modem_get_manufacturer
|
||||
mm_gdbus_modem_dup_manufacturer
|
||||
mm_gdbus_modem_get_max_active_bearers
|
||||
mm_gdbus_modem_get_max_active_multiplexed_bearers
|
||||
mm_gdbus_modem_get_max_bearers
|
||||
mm_gdbus_modem_get_model
|
||||
mm_gdbus_modem_dup_model
|
||||
@@ -2193,6 +2195,7 @@ mm_gdbus_modem_set_drivers
|
||||
mm_gdbus_modem_set_equipment_identifier
|
||||
mm_gdbus_modem_set_manufacturer
|
||||
mm_gdbus_modem_set_max_active_bearers
|
||||
mm_gdbus_modem_set_max_active_multiplexed_bearers
|
||||
mm_gdbus_modem_set_max_bearers
|
||||
mm_gdbus_modem_set_model
|
||||
mm_gdbus_modem_set_own_numbers
|
||||
|
Reference in New Issue
Block a user