mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager
synced 2024-07-20 17:55:49 +00:00
2140dad5e0
These days more and more devices are showing up that support a number of different access technology families in the same hardware, like Qualcomm Gobi (CDMA and GSM), Pantech UM190 (CDMA and GSM), Pantech UML290 (CDMA and LTE), LG VL600 (CDMA and LTE), Sierra 320U (GSM and LTE), etc. The previous scheme of having device classes based on access technology family simply cannot handle this hardware and attempting to add LTE to both the CDMA and GSM device classes would result in a bunch of code duplication that we don't want. There's a better way... Instead, combine both CDMA and GSM device classes into a generic "Modem" device class that provides capabilities indicating what access technology families a modem supports, and what families it supports immediately without a firmware reload. (Gobi devices for example require a firmware reload before they can switch between GSM and CDMA). This provides the necessary flexibility to the client and allows us to keep the API stable when the same consolidation change is made in ModemManager. The current code doesn't yet allow multi-mode operation internally, but the API is now what we want it to be and won't need to be changed.
65 lines
2.4 KiB
XML
65 lines
2.4 KiB
XML
<?xml version="1.0" encoding="UTF-8" ?>
|
|
|
|
<node name="/" xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
|
|
<interface name="org.freedesktop.NetworkManager.Device.Modem">
|
|
|
|
<signal name="PropertiesChanged">
|
|
<arg name="properties" type="a{sv}" tp:type="String_Variant_Map">
|
|
<tp:docstring>
|
|
A dictionary mapping property names to variant boxed values
|
|
</tp:docstring>
|
|
</arg>
|
|
</signal>
|
|
|
|
<property name="ModemCapabilities" type="u" access="read" tp:type="NM_DEVICE_MODEM_CAPABILITIES">
|
|
<tp:docstring>
|
|
The generic family of access technologies the modem supports. Not all
|
|
capabilities are available at the same time however; some modems require
|
|
a firmware reload or other reinitialization to switch between eg CDMA/EVDO
|
|
and GSM/UMTS.
|
|
</tp:docstring>
|
|
</property>
|
|
|
|
<property name="CurrentCapabilities" type="u" access="read" tp:type="NM_DEVICE_MODEM_CAPABILITIES">
|
|
<tp:docstring>
|
|
The generic family of access technologies the modem currently supports
|
|
without a firmware reload or reinitialization.
|
|
</tp:docstring>
|
|
</property>
|
|
|
|
<tp:flags name="NM_DEVICE_MODEM_CAPABILITIES" value-prefix="NM_DEVICE_MODEM_CAPABILITY" type="u">
|
|
<tp:docstring>
|
|
Flags describing one or more of the general access technology families
|
|
that a modem device supports.
|
|
</tp:docstring>
|
|
<tp:flag suffix="NONE" value="0x0">
|
|
<tp:docstring>Modem has no capabilties.</tp:docstring>
|
|
</tp:flag>
|
|
<tp:flag suffix="POTS" value="0x1">
|
|
<tp:docstring>
|
|
Modem supports the analog wired telephone network (ie 56k dialup) and
|
|
does not have wireless/cellular capabilities.
|
|
</tp:docstring>
|
|
</tp:flag>
|
|
<tp:flag suffix="CDMA_EVDO" value="0x2">
|
|
<tp:docstring>
|
|
Modem supports at least one of CDMA 1xRTT, EVDO revision 0, EVDO
|
|
revision A, or EVDO revision B.
|
|
</tp:docstring>
|
|
</tp:flag>
|
|
<tp:flag suffix="GSM_UMTS" value="0x4">
|
|
<tp:docstring>
|
|
Modem supports at least one of GSM, GPRS, EDGE, UMTS, HSDPA, HSUPA, or
|
|
HSPA+ packet switched data capability.
|
|
</tp:docstring>
|
|
</tp:flag>
|
|
<tp:flag suffix="LTE" value="0x8">
|
|
<tp:docstring>
|
|
Modem has at LTE data capability.
|
|
</tp:docstring>
|
|
</tp:flag>
|
|
</tp:flags>
|
|
|
|
</interface>
|
|
</node>
|