diff options
| author | Michael Biebl <biebl@debian.org> | 2012-06-29 20:12:44 +0200 |
|---|---|---|
| committer | Michael Biebl <biebl@debian.org> | 2012-06-29 20:12:44 +0200 |
| commit | 867254ea7c2b193fecf8cd36cc6e5dc53c290d92 (patch) | |
| tree | 7c698b403882736ab70c3efd524c3460f08c391c /introspection/nm-device.xml | |
| parent | de06e5715e780baade318f3490ac7a4c9ce84e32 (diff) | |
Imported Upstream version 0.9.5.95 upstream/0.9.5.95
Diffstat (limited to 'introspection/nm-device.xml')
| -rw-r--r-- | introspection/nm-device.xml | 23 |
1 files changed, 23 insertions, 0 deletions
diff --git a/introspection/nm-device.xml b/introspection/nm-device.xml index d12d4778..7f6a0a07 100644 --- a/introspection/nm-device.xml +++ b/introspection/nm-device.xml @@ -36,6 +36,16 @@ The driver handling the device. </tp:docstring> </property> + <property name="DriverVersion" type="s" access="read"> + <tp:docstring> + The version of the driver handling the device. + </tp:docstring> + </property> + <property name="FirmwareVersion" type="s" access="read"> + <tp:docstring> + The firmware version for 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. @@ -91,6 +101,14 @@ Whether or not this device is managed by NetworkManager. </tp:docstring> </property> + <property name="Autoconnect" type="b" access="readwrite"> + <tp:docstring> + If TRUE, indicates the device is allowed to autoconnect. If FALSE, + manual intervention is required before the device will automatically + connect to a known network, such as activating a connection using the + device, or setting this property to TRUE. + </tp:docstring> + </property> <property name="FirmwareMissing" type="b" access="read"> <tp:docstring> If TRUE, indicates the device is likely missing firmware necessary for @@ -526,6 +544,11 @@ A dependency of the connection failed. </tp:docstring> </tp:enumvalue> + <tp:enumvalue suffix="BR2684_FAILED" value="50"> + <tp:docstring> + Problem with the RFC 2684 Ethernet over ADSL bridge. + </tp:docstring> + </tp:enumvalue> </tp:enum> <tp:struct name="NM_DEVICE_STATE_REASON_STRUCT"> |