summaryrefslogtreecommitdiffstats
path: root/knetworkmanager-0.9/introspection/nm-device.xml
diff options
context:
space:
mode:
authorTimothy Pearson <[email protected]>2012-08-30 12:33:38 -0500
committerTimothy Pearson <[email protected]>2012-08-30 12:33:38 -0500
commitbf231a0d0362758f167da389222e271acb2ebd90 (patch)
tree5d2f65ec8c2608fd54b61858293cd2a9afab483f /knetworkmanager-0.9/introspection/nm-device.xml
parent4d89fd747ffbf3493b647cb4ff5380d1fc8f328d (diff)
downloadtdenetworkmanager-bf231a0d0362758f167da389222e271acb2ebd90.tar.gz
tdenetworkmanager-bf231a0d0362758f167da389222e271acb2ebd90.zip
Remove Automake, introspection files, etc. in preparation for future development
Diffstat (limited to 'knetworkmanager-0.9/introspection/nm-device.xml')
-rw-r--r--knetworkmanager-0.9/introspection/nm-device.xml126
1 files changed, 0 insertions, 126 deletions
diff --git a/knetworkmanager-0.9/introspection/nm-device.xml b/knetworkmanager-0.9/introspection/nm-device.xml
deleted file mode 100644
index 848942a..0000000
--- a/knetworkmanager-0.9/introspection/nm-device.xml
+++ /dev/null
@@ -1,126 +0,0 @@
-<?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">
- <property name="Udi" type="s" access="read">
- <tp:docstring>
- HAL UDI for the device.
- </tp:docstring>
- </property>
- <property name="Interface" type="s" access="read">
- <tp:docstring>
- The network interface offered by the device.
- </tp:docstring>
- </property>
- <property name="Driver" type="s" access="read">
- <tp:docstring>
- The driver handling the device.
- </tp:docstring>
- </property>
- <property name="Capabilities" type="u" access="read" tp:type="NM_DEVICE_CAP">
- <tp:docstring>
- Flags describing the capabilities of the device.
- </tp:docstring>
- </property>
- <property name="Ip4Address" type="i" access="read">
- <tp:docstring>
- The IPv4 address bound to the device. FIXME: what about devices with >1 IP address?
- </tp:docstring>
- </property>
- <property name="State" type="u" access="read" tp:type="NM_DEVICE_STATE">
- <tp:docstring>
- The current state of the device.
- </tp:docstring>
- </property>
- <property name="Ip4Config" type="o" access="read">
- <tp:docstring>
- Object path of the Ip4Config object describing the configuration of the device. Only valid when the device is in the NM_DEVICE_STATE_ACTIVATED state.
- </tp:docstring>
- </property>
- <property name="Managed" type="b" access="read">
- <tp:docstring>
- Whether or not this device is managed by NetworkManager.
- </tp:docstring>
- </property>
-
- <!-- Ugh, but I see no other way of getting the type on the caller
- based on dbus object path only -->
- <property name="DeviceType" type="u" access="read">
- <tp:docstring>
- </tp:docstring>
- </property>
-
-
- <signal name="StateChanged">
- <arg name="state" type="u" tp:type="NM_DEVICE_STATE">
- <tp:docstring>
- The new state of the device.
- </tp:docstring>
- </arg>
- </signal>
-
- <tp:enum name="NM_DEVICE_STATE" type="u">
- <tp:enumvalue suffix="UNKNOWN" value="0">
- <tp:docstring>
- The device is in an unknown state.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="DOWN" value="1">
- <tp:docstring>
- The device is down.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="DISCONNECTED" value="2">
- <tp:docstring>
- The device is not connected.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="PREPARE" value="3">
- <tp:docstring>
- The device is preparing to connect.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="CONFIG" value="4">
- <tp:docstring>
- The device is being configured.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="NEED_AUTH" value="5">
- <tp:docstring>
- The device is awaiting authorization credentials.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="IP_CONFIG" value="6">
- <tp:docstring>
- The IP address of the device is being configured.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="ACTIVATED" value="7">
- <tp:docstring>
- The device is active.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="FAILED" value="8">
- <tp:docstring>
- The device is in a failure state following an attempt to activate it.
- </tp:docstring>
- </tp:enumvalue>
- <tp:enumvalue suffix="CANCELLED" value="9">
- <tp:docstring>
- The previous activation attempt on this device was cancelled.
- </tp:docstring>
- </tp:enumvalue>
- </tp:enum>
- <tp:flags name="NM_DEVICE_CAP" value-prefix="NM_DEVICE_CAP" type="u">
- <tp:flag suffix="NONE" value="0x0">
- <tp:docstring>Null capability.</tp:docstring>
- </tp:flag>
- <tp:flag suffix="NM_SUPPORTED" value="0x1">
- <tp:docstring>The device is supported by NetworkManager.</tp:docstring>
- </tp:flag>
- <tp:flag suffix="CARRIER_DETECT" value="0x2">
- <tp:docstring>The device supports carrier detection.</tp:docstring>
- </tp:flag>
- </tp:flags>
- </interface>
-</node>