SymbX/ModemManager
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

api,enums: implement all enums and flags from the new API

Browse Source
This commit is contained in:
Aleksander Morgado
2012-03-15 14:14:17 +01:00
parent 8763576a34
commit 4cdbaa5de3
8 changed files with 455 additions and 743 deletions
Download Patch File Download Diff File Expand all files Collapse all files
new/org.freedesktop.ModemManager1.Bearer.xml
-21
View File
@@ -228,26 +228,5 @@
-->
<property name="Ip6Config" type="a{sv}" access="read" />
<!-- ENUMS -->
<tp:enum name="MM_MODEM_BEARER_IP_METHOD" type="u">
<tp:enumvalue suffix="PPP" value="0">
<tp:docstring>
Connection managers should use PPP to get the address.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="STATIC" value="1">
<tp:docstring>
Connection managers should use the provided static IP configuration
given by the modem to configure the IP data interface.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="DHCP" value="2">
<tp:docstring>
Connection managers should begin DHCP on the data interface to obtain
necessary IP configuration details.
</tp:docstring>
</tp:enumvalue>
</tp:enum>
</interface>
</node>
new/org.freedesktop.ModemManager1.Modem.3gpp.xml
-38
View File
@@ -138,44 +138,6 @@
-->
<property name="EnabledFacilityLocks" type="u" access="read" />
<!-- ENUMS -->
<tp:enum name="MM_MODEM_3GPP_REGISTRATION_STATE" type="u">
<tp:docstring>
GSM registration code as defined in 3GPP TS 27.007 section 10.1.19.
</tp:docstring>
<tp:enumvalue suffix="IDLE" value="0">
<tp:docstring>
Not registered, not searching for new operator to register.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="HOME" value="1">
<tp:docstring>
Registered on home network.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SEARCHING" value="2">
<tp:docstring>
Not registered, searching for new operator to register with.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="DENIED" value="3">
<tp:docstring>
Registration denied.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="UNKNOWN" value="4">
<tp:docstring>
Unknown registration status.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="ROAMING" value="5">
<tp:docstring>
Registered on a roaming network.
</tp:docstring>
</tp:enumvalue>
</tp:enum>
</interface>
</node>
new/org.freedesktop.ModemManager1.Modem.Cdma.xml
-80
View File
@@ -120,85 +120,5 @@
-->
<property name="EvdoRegistrationState" type="u" access="read" />
<!-- ENUMS -->
<tp:enum name="MM_MODEM_CDMA_REGISTRATION_STATE" type="u">
<tp:enumvalue suffix="UNKNOWN" value="0">
<tp:docstring>Registration status is unknown or the device is not registered.</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="REGISTERED" value="1">
<tp:docstring>Registered, but roaming status is unknown or cannot be provided by the device. The device may or may not be roaming.</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="HOME" value="2">
<tp:docstring>Currently registered on the home network.</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="ROAMING" value="3">
<tp:docstring>Currently registered on a roaming network.</tp:docstring>
</tp:enumvalue>
</tp:enum>
<tp:enum name="MM_MODEM_CDMA_ACTIVATION_STATE" type="u">
<tp:enumvalue suffix="NOT_ACTIVATED" value="0">
<tp:docstring>Device is not activated</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="ACTIVATING" value="1">
<tp:docstring>Device is activating</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PARTIALLY_ACTIVATED" value="2">
<tp:docstring>Device is partially activated; carrier-specific steps required to continue.</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="ACTIVATED" value="3">
<tp:docstring>Device is ready for use.</tp:docstring>
</tp:enumvalue>
</tp:enum>
<tp:enum name="MM_MODEM_CDMA_ACTIVATION_ERROR" type="u">
<tp:enumvalue suffix="NO_ERROR" value="0"/>
<tp:enumvalue suffix="ROAMING" value="1">
<tp:docstring>
Device cannot activate while roaming.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="WRONG_RADIO_INTERFACE" value="2">
<tp:docstring>
Device cannot activate on this network type (eg EVDO vs 1xRTT).
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="COULD_NOT_CONNECT" value="3">
<tp:docstring>
Device could not connect to the network for activation.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SECURITY_AUTHENTICATION_FAILED" value="4">
<tp:docstring>
Device could not authenticate to the network for activation.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PROVISIONING_FAILED" value="5">
<tp:docstring>
Later stages of device provisioning failed.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="NO_SIGNAL" value="6">
<tp:docstring>
No signal available.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="UNKNOWN" value="7">
<tp:docstring>
An error occurred.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="TIMED_OUT" value="8">
<tp:docstring>
Activation timed out.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="START_FAILED" value="9">
<tp:docstring>
API call for initial activation failed.
</tp:docstring>
</tp:enumvalue>
</tp:enum>
</interface>
</node>
new/org.freedesktop.ModemManager1.Modem.Contacts.xml
-23
View File
@@ -173,28 +173,5 @@
<arg name="index" type="u" />
</signal>
<!-- ENUMS -->
<tp:enum name="MM_MODEM_CONTACTS_STORAGE" type="u">
<tp:docstring>
Specifies different storage locations for contact information.
</tp:docstring>
<tp:enumvalue suffix="ME" value="0">
<tp:docstring>
Store information in device's local memory.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SM" value="1">
<tp:docstring>
Store information in a card inserted in the device (like a SIM/RUIM).
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="MT" value="2">
<tp:docstring>
Store information in the combined device/ME and SIM/SM phonebook.
</tp:docstring>
</tp:enumvalue>
</tp:enum>
</interface>
</node>
new/org.freedesktop.ModemManager1.Modem.Location.xml
-143
View File
@@ -247,149 +247,6 @@
-->
<property name="Location" type="a{uv}" access="read" />
<!-- ENUMS -->
<tp:flags name="MM_MODEM_LOCATION_CAPABILITIES" value-prefix="MM_MODEM_LOCATION_CAPABILITY" type="u">
<tp:flag suffix="UNKNOWN" value="0x0">
<tp:docstring><p>Unknown or no capabilties.</p></tp:docstring>
</tp:flag>
<tp:flag suffix="GPS_NMEA" value="0x1">
<tp:docstring>
<p>For capability reporting, indicates the device is capable of
providing GPS NMEA-format location information.</p>
<p>For location reporting, devices supporting this capability return
a string containing one or more NMEA sentences (D-Bus signature 's').
The manager will cache the most recent NMEA sentence of each type for
a period of time not less than 30 seconds. When reporting multiple
NMEA sentences, sentences shall be separated by an ASCII Carriage
Return and Line Feed (&lt;CR&gt;&lt;LF&gt;) sequence.
</p>
<p>
For example, if the device sends a $GPRMC sentence immediately
followed by a $GPGGA sentence, the reported location string would be
(where of course the &lt;CR&gt;&lt;LF&gt; is replaced with the actual
ASCII CR (0x0D) and LF (0x0A) control characters):
<pre>
$GPRMC,134523.92,V,,,,,,,030136,,,N*73&lt;CR&gt;&lt;LF&gt;$GPGGA,,,,,,0,00,0.5,,M,0.0001999,M,0.0000099,0000*45
</pre>
If the device sends a new $GPRMC three seconds later, the new $GPRMC
replaces the previously received $GPRMC sentence, and the updated
string would be:
<pre>
$GPRMC,134526.92,V,,,,,,,030136,,,N*76&lt;CR&gt;&lt;LF&gt;$GPGGA,,,,,,0,00,0.5,,M,0.0001999,M,0.0000099,0000*45
</pre>
If the device then sends a $GPGSA sentence about 5 seconds later, the
$GPGSA sentence is added to the string (since no $GPGSA sentence was
previously received in this session), the updated string would be:
<pre>
$GPRMC,134526.92,V,,,,,,,030136,,,N*76&lt;CR&gt;&lt;LF&gt;$GPGGA,,,,,,0,00,0.5,,M,0.0001999,M,0.0000099,0000*45&lt;CR&gt;&lt;LF&gt;$GPGSA,A,1,,,,,,,,,,,,,1.1,0.5,1.0*34
</pre>
The manager may discard any cached sentences older than 30 seconds.
</p>
<p>This allows clients to read the latest positioning data as soon as
possible after they start, even if the device is not providing
frequent location data updates.
</p>
</tp:docstring>
</tp:flag>
<tp:flag suffix="GSM_LAC_CI" value="0x2">
<tp:docstring>
<p>For capability reporting, indicates the device is capable of
providing GSM Location Area Code/Cell ID location information.</p>
<p>For location reporting, devices supporting this
capability return a string in the format "MCC,MNC,LAC,CI" (without the
quotes of course) where the following applies:</p>
<ul>
<li>
MCC is the three-digit ITU E.212 Mobile Country Code of the
network provider to which the mobile is currently registered.
This value should be the same MCC as reported by the
org.freedesktop.Modem.Gsm.Network.GetRegistrationInfo() method's
returned "operator code" argument.
e.g. "310"
</li>
<li>
MNC is the two- or three-digit GSM Mobile Network Code of the
network provider to which the mobile is currently registered.
This value should be the same MCC as reported by the
org.freedesktop.Modem.Gsm.Network.GetRegistrationInfo() method's
returned "operator code" argument.
e.g. "26" or "260"
</li>
<li>
LAC is the two-byte Location Area Code of the base station with
which the mobile is registered, in upper-case hexadecimal format
without leading zeros, as specified in 3GPP TS 27.007 section
10.1.19. e.g. "84CD".
</li>
<li>
CI is the two- or four-byte Cell Identifier with which the mobile
is registered, in upper-case hexadecimal format without leading
zeros, as specified in 3GPP TS 27.007. e.g. "2BAF" or "D30156".
</li>
</ul>
<p>The entire string may only be composed of the ASCII digits [0-9],
the alphabetical characters [A-F], and the comma (,) character. No
other characters are allowed. For example: "310,260,8BE3,2BAF" or
"250,40,CE00,1CEAD8F0".</p>
<p>If any of these four items (MCC,MNC,LAC,CI) is unknown or the
mobile is not registered with a network, then the GSM_LAC_CI location
information item should not be provided as a returned value from the
GetLocation() method or in the Location property.</p>
</tp:docstring>
</tp:flag>
<tp:flag suffix="GPS_RAW" value="0x4">
<tp:docstring>
<p>For capability reporting, indicates the device is capable of
providing raw GPS information using a series of defined key/value
pairs.</p>
<p>For location reporting, devices supporting this
capability return a D-Bus dict (signature a{sv}) mapping well-known
keys to values with defined formats. The allowed key/value pairs
and their formats are:</p>
<table>
<tr><th>Key</th><th>Value Type</th><th>Value contents</th><th>Example</th></tr>
<tr>
<td>latitude</td>
<td>d</td>
<td>Latitude in Decimal Degrees (positive numbers mean N quadrasphere, negative mean S quadrasphere)</td>
<td>38.889722 (ie, 38d 53' 22" N)</td>
</tr>
<tr>
<td>longitude</td>
<td>d</td>
<td>Longitude in Decimal Degrees (positive numbers mean E quadrasphere, negative mean W quadrasphere)</td>
<td>-77.008889 (ie, 77d 0' 32" W)</td>
</tr>
<tr>
<td>altitude</td>
<td>d</td>
<td>Altitude above sea level in meters</td>
<td>33.5</td>
</tr>
<tr>
<td>horiz-velocity</td>
<td>d</td>
<td>Horizontal velocity in meters-per-second</td>
<td>.5</td>
</tr>
<tr>
<td>vert-velocity</td>
<td>d</td>
<td>Vertical velocity in meters-per-second</td>
<td>.01</td>
</tr>
</table>
<p>The 'latitude' and 'longitude' keys are required; other keys are
optional.</p>
</tp:docstring>
</tp:flag>
</tp:flags>
</interface>
</node>
new/org.freedesktop.ModemManager1.Modem.xml
-403
View File
@@ -415,408 +415,5 @@
-->
<property name="AllowedBands" type="t" access="read" />
<!-- ENUMS -->
<tp:flags name="MM_MODEM_CAPABILITIES" value-prefix="MM_MODEM_CAPABILITY" type="u">
<tp:docstring>
Flags describing one or more of the general access technology families
that a modem 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 LTE data capability.
</tp:docstring>
</tp:flag>
<tp:flag suffix="LTE_ADVANCED" value="0x10">
<tp:docstring>
Modem has LTE Advanced data capability.
</tp:docstring>
</tp:flag>
</tp:flags>
<tp:enum name="MM_MODEM_LOCK" type="u">
<tp:enumvalue suffix="UNKNOWN" value="0">
<tp:docstring>
Lock reason unknown.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="NONE" value="1">
<tp:docstring>
Modem is unlocked.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SIM_PIN" value="2">
<tp:docstring>
SIM requires the PIN code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SIM_PIN2" value="3">
<tp:docstring>
SIM requires the PIN2 code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SIM_PUK" value="4">
<tp:docstring>
SIM requires the PUK code
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SIM_PUK2" value="5">
<tp:docstring>
SIM requires the PUK2 code
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_SP_PIN" value="6">
<tp:docstring>
Modem requires the service provider PIN code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_SP_PUK" value="7">
<tp:docstring>
Modem requires the service provider PUK code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_NET_PIN" value="8">
<tp:docstring>
Modem requires the network PIN code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_NET_PUK" value="9">
<tp:docstring>
Modem requires the network PUK code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_SIM_PIN" value="10">
<tp:docstring>
Modem requires the PIN code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_CORP_PIN" value="11">
<tp:docstring>
Modem requires the corporate PIN code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_CORP_PUK" value="12">
<tp:docstring>
Modem requires the corporate PUK code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_FSIM_PIN" value="13">
<tp:docstring>
Modem requires the FSIM-PIN code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_FSIM_PUK" value="14">
<tp:docstring>
Modem requires the FSIM-PUK code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_NETSUB_PIN" value="15">
<tp:docstring>
Modem requires the network subset PIN code.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="PH_NETSUB_PUK" value="16">
<tp:docstring>
Modem requires the network subset PUK code.
</tp:docstring>
</tp:enumvalue>
</tp:enum>
<tp:enum name="MM_MODEM_STATE" type="u">
<tp:enumvalue suffix="UNKNOWN" value="0">
<tp:docstring>
State unknown or not reportable.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="DISABLED" value="10">
<tp:docstring>
The modem is not enabled and is powered down.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="DISABLING" value="20">
<tp:docstring>
The modem is current transitioning to the DISABLED state.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="ENABLING" value="30">
<tp:docstring>
The modem is currently transitioning to the ENABLED state.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="ENABLED" value="40">
<tp:docstring>
The modem is enabled and powered on but not registered with a network
provider and not available for data connections.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SEARCHING" value="50">
<tp:docstring>
The modem is searching for a network provider to register with.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="REGISTERED" value="60">
<tp:docstring>
The modem is registered with a network provider, and data connections
and messaging may be available for use.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="DISCONNECTING" value="70">
<tp:docstring>
The modem is disconnecting and deactivating the last active packet
data bearer. This state will not be entered if more than one packet
data bearer is active and one of the active bearers is deactivated.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="CONNECTING" value="80">
<tp:docstring>
The modem is activating and connecting the first packet data bearer.
Subsequent bearer activations when another bearer is already active
do not cause this state to be entered.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="CONNECTED" value="90">
<tp:docstring>
One or more packet data bearers is active and connected.
</tp:docstring>
</tp:enumvalue>
</tp:enum>
<tp:enum name="MM_MODEM_STATE_CHANGED_REASON" type="u">
<tp:enumvalue suffix="UNKNOWN" value="0">
<tp:docstring>
Reason unknown or not reportable.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="USER_REQUESTED" value="1">
<tp:docstring>
State change was requested by an interface user.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SUSPEND" value="2">
<tp:docstring>
State change was caused by a system suspend.
</tp:docstring>
</tp:enumvalue>
</tp:enum>
<tp:enum name="MM_MODEM_ACCESS_TECH" type="u">
<tp:docstring>
Describes various access technologies that a device uses when registered
with or connected to a network.
</tp:docstring>
<tp:enumvalue suffix="UNKNOWN" value="0">
<tp:docstring>The access technology used is unknown</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="POTS" value="1">
<tp:docstring>Analog wireline telephone</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="GSM" value="2">
<tp:docstring>GSM</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="GSM_COMPACT" value="3">
<tp:docstring>Compact GSM</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="GPRS" value="4">
<tp:docstring>GPRS</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="EDGE" value="5">
<tp:docstring>EDGE (ETSI 27.007: "GSM w/EGPRS")</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="UMTS" value="6">
<tp:docstring>UMTS (ETSI 27.007: "UTRAN")</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="HSDPA" value="7">
<tp:docstring>HSDPA (ETSI 27.007: "UTRAN w/HSDPA")</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="HSUPA" value="8">
<tp:docstring>HSUPA (ETSI 27.007: "UTRAN w/HSUPA")</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="HSPA" value="9">
<tp:docstring>HSPA (ETSI 27.007: "UTRAN w/HSDPA and HSUPA")</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="HSPA_PLUS" value="10">
<tp:docstring>HSPA+ (ETSI 27.007: "UTRAN w/HSPA+")</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="1XRTT" value="11">
<tp:docstring>CDMA2000 1xRTT</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="EVDO0" value="12">
<tp:docstring>CDMA2000 EVDO revision 0</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="EVDOA" value="13">
<tp:docstring>CDMA2000 EVDO revision A</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="EVDOB" value="14">
<tp:docstring>CDMA2000 EVDO revision B</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="LTE" value="15">
<tp:docstring>LTE (ETSI 27.007: "E-UTRAN")</tp:docstring>
</tp:enumvalue>
</tp:enum>
<tp:enum name="MM_MODEM_MODE" type="u">
<tp:docstring>
Bitfield to indicate which access modes are supported, allowed or
preferred in a given device.
</tp:docstring>
<tp:enumvalue suffix="NONE" value="0x00">
<tp:docstring>None</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="1G" value="0x01">
<tp:docstring>CSD, GSM</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="2G" value="0x02">
<tp:docstring>GPRS, EDGE</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="3G" value="0x04">
<tp:docstring>UMTS, HSxPA</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="4G" value="0x08">
<tp:docstring>LTE</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="ANY" value="0xFFFFFFFF">
<tp:docstring>
Any mode can be used (only this value allowed for POTS modems)
</tp:docstring>
</tp:enum>
<tp:flags name="MM_MODEM_BAND" value-prefix="MM_MODEM_BAND" type="u">
<tp:docstring>
A 64-bit wide bitfield describing the specific radio bands supported by
the device and the radio bands the device is allowed to use when
connecting to a mobile network.
</tp:docstring>
<tp:flag suffix="UNKNOWN" value="0x0">
<tp:docstring>Unknown or invalid band</tp:docstring>
</tp:flag>
<tp:flag suffix="ANY" value="0x1">
<tp:docstring>For certain operations, allow the modem to select a band automatically.</tp:docstring>
</tp:flag>
<!-- GSM/UMTS/3GPP bands -->
<tp:flag suffix="EGSM" value="0x2">
<tp:docstring>GSM/GPRS/EDGE 900 MHz</tp:docstring>
</tp:flag>
<tp:flag suffix="DCS" value="0x4">
<tp:docstring>GSM/GPRS/EDGE 1800 MHz</tp:docstring>
</tp:flag>
<tp:flag suffix="PCS" value="0x8">
<tp:docstring>GSM/GPRS/EDGE 1900 MHz</tp:docstring>
</tp:flag>
<tp:flag suffix="G850" value="0x10">
<tp:docstring>GSM/GPRS/EDGE 850 MHz</tp:docstring>
</tp:flag>
<tp:flag suffix="U2100" value="0x20">
<tp:docstring>WCDMA 2100 MHz (Class I)</tp:docstring>
</tp:flag>
<tp:flag suffix="U1800" value="0x40">
<tp:docstring>WCDMA 3GPP 1800 MHz (Class III)</tp:docstring>
</tp:flag>
<tp:flag suffix="U17IV" value="0x80">
<tp:docstring>WCDMA 3GPP AWS 1700/2100 MHz (Class IV)</tp:docstring>
</tp:flag>
<tp:flag suffix="U800" value="0x100">
<tp:docstring>WCDMA 3GPP UMTS 800 MHz (Class VI)</tp:docstring>
</tp:flag>
<tp:flag suffix="U850" value="0x200">
<tp:docstring>WCDMA 3GPP UMTS 850 MHz (Class V)</tp:docstring>
</tp:flag>
<tp:flag suffix="U900" value="0x400">
<tp:docstring>WCDMA 3GPP UMTS 900 MHz (Class VIII)</tp:docstring>
</tp:flag>
<tp:flag suffix="U17IX" value="0x800">
<tp:docstring>WCDMA 3GPP UMTS 1700 MHz (Class IX)</tp:docstring>
</tp:flag>
<tp:flag suffix="U1900" value="0x1000">
<tp:docstring>WCDMA 3GPP UMTS 1900 MHz (Class II)</tp:docstring>
</tp:flag>
<tp:flag suffix="U2600" value="0x2000">
<tp:docstring>WCDMA 3GPP UMTS 2600 MHz (Class VII, internal)</tp:docstring>
</tp:flag>
<!-- CDMA Band Classes (see 3GPP2 C.S0057-C) -->
<tp:flag suffix="CDMA_BC0_CELLULAR_800" value="0x0000000100000000">
<tp:docstring>CDMA Band Class 0 (US Cellular 850MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC1_PCS_1900" value="0x0000000200000000">
<tp:docstring>CDMA Band Class 1 (US PCS 1900MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC2_TACS" value="0x0000000400000000">
<tp:docstring>CDMA Band Class 2 (UK TACS 900MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC3_JTACS" value="0x0000000800000000">
<tp:docstring>CDMA Band Class 3 (Japanese TACS)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC4_KOREAN_PCS" value="0x0000001000000000">
<tp:docstring>CDMA Band Class 4 (Korean PCS)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC5_NMT450" value="0x0000002000000000">
<tp:docstring>CDMA Band Class 5 (NMT 450MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC6_IMT2000" value="0x0000004000000000">
<tp:docstring>CDMA Band Class 6 (IMT2000 2100MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC7_CELLULAR_700" value="0x0000008000000000">
<tp:docstring>CDMA Band Class 7 (Cellular 700MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC8_1800" value="0x0000010000000000">
<tp:docstring>CDMA Band Class 8 (1800MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC9_900" value="0x0000020000000000">
<tp:docstring>CDMA Band Class 9 (900MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC10_SECONDARY_800" value="0x0000040000000000">
<tp:docstring>CDMA Band Class 10 (US Secondary 800)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC11_PAMR_400" value="0x0000080000000000">
<tp:docstring>CDMA Band Class 11 (European PAMR 400MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC12_PAMR_800" value="0x0000100000000000">
<tp:docstring>CDMA Band Class 12 (PAMR 800MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC13_IMT2000_2500" value="0x0000200000000000">
<tp:docstring>CDMA Band Class 13 (IMT2000 2500MHz Expansion)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC14_PCS2_1900" value="0x0000400000000000">
<tp:docstring>CDMA Band Class 14 (More US PCS 1900MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC15_AWS" value="0x0000800000000000">
<tp:docstring>CDMA Band Class 15 (AWS 1700MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC16_US_2500" value="0x0001000000000000">
<tp:docstring>CDMA Band Class 16 (US 2500MHz)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC17_US_FLO_2500" value="0x0002000000000000">
<tp:docstring>CDMA Band Class 17 (US 2500MHz Forward Link Only)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC18_US_PS_700" value="0x0004000000000000">
<tp:docstring>CDMA Band Class 18 (US 700MHz Public Safety)</tp:docstring>
</tp:flag>
<tp:flag suffix="CDMA_BC19_US_LOWER_700" value="0x0008000000000000">
<tp:docstring>CDMA Band Class 19 (US Lower 700MHz)</tp:docstring>
</tp:flag>
</tp:flags>
</interface>
</node>
new/org.freedesktop.ModemManager1.Sms.xml
-35
View File
@@ -94,40 +94,5 @@
-->
<property name="Timestamp" type="s" access="read" />
<!-- ENUMS -->
<tp:enum name="MM_MODEM_SMS_STATE" type="u">
<tp:enumvalue suffix="UNKNOWN" value="0">
<tp:docstring>
State unknown or not reportable.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="STORED" value="0">
<tp:docstring>
The message has been neither received nor yet sent.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="RECEIVING" value="1">
<tp:docstring>
The message is being received but is not yet complete.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="RECEIVED" value="2">
<tp:docstring>
The message received and is complete.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SENDING" value="3">
<tp:docstring>
The message is queued for delivery.
</tp:docstring>
</tp:enumvalue>
<tp:enumvalue suffix="SENT" value="4">
<tp:docstring>
The message was successfully sent.
</tp:docstring>
</tp:enumvalue>
</tp:enum>
</interface>
</node>