fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2025-12-21 11:00:07 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/introspection/Makefile.am

35 lines
723 B
Text
Raw Normal View History

Add missing introspection files to tarball (Robert Piasek) git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@4023 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-28 14:12:09 +00:00
EXTRA_DIST = \
api: update version based on configure version Instead of manually which is error-prone.
2011-08-06 10:59:19 +02:00
all.xml.in \
Add missing introspection files to tarball (Robert Piasek) git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@4023 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-28 14:12:09 +00:00
generic-types.xml \
errors.xml \
vpn-errors.xml \
nm-access-point.xml \
build: add BT introspection to dist tarball
2009-07-28 10:12:27 -04:00
nm-device-bt.xml \
Add missing introspection files to tarball (Robert Piasek) git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@4023 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-28 14:12:09 +00:00
nm-device-wifi.xml \
olpc: add mesh device logic and config setting
2009-08-05 16:34:02 -04:00
nm-device-olpc-mesh.xml \
Add missing introspection files to tarball (Robert Piasek) git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@4023 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-28 14:12:09 +00:00
nm-device-ethernet.xml \
adsl: settings and initial "scaffolding" This patch adds the settings code (NMSettingAdsl) and the initial "scaffolding" i.e., a tiny stub version of NMDeviceAdsl and the udev handler code to get the device detected. With this patch you should be able to see an atm device being detected by networkmanager in the logs, although of course it doesn't do anything useful yet. Extract from the logs: [1304668252.341354] [nm-udev-manager.c:562] adsl_add(): adsl_add: ATM Device detected from udev. Adding .. (ueagle-atm0): failed to look up interface index (ueagle-atm0): new ADSL device (driver: 'ueagle-atm' ifindex: -1) (ueagle-atm0): exported as /org/freedesktop/NetworkManager/Devices/2 (ueagle-atm0): now managed (ueagle-atm0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] (ueagle-atm0): deactivating device (reason: 2). [1304668252.345102] [nm-system.c:1349] flush_routes(): (ueagle-atm0) failed to lookup interface index [1304668252.347821] [nm-device.c:3912] nm_device_state_changed(): (ueagle-atm0): device is available, In this version, we hack the nm-device.c:nm_device_get_priority() to get better priority instead of changing the DeviceType enum. Signed-off-by: Pantelis Koukousoulas <pktoss@gmail.com>
2011-05-17 21:03:18 +03:00
nm-device-adsl.xml \
core: consolidate mobile broadband device types 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.
2011-02-25 10:16:17 -06:00
nm-device-modem.xml \
wimax: make WiMAX mostly work Heavily modify Inaky's Intel WiMAX SDK glue (originally from connman) to be more generic and more thread-safe, and suitable for use with NetworkManager instead of rolling our own client code. Rewrite the NMDeviceWimax code to mostly work. Still to be done: actual connection logic, DHCP handling, spawning wimaxd if it's not started yet
2011-01-03 23:55:38 -06:00
nm-device-wimax.xml \
api: fix various Infiniband introspection XML omissions
2012-02-13 17:43:04 -06:00
nm-device-infiniband.xml \
bond: move bond master interfaces to NMDeviceBond This way clients know it's a bond master, and it allows us to more cleanly separate the code for bonding and non-bonding cases.
2012-02-15 17:31:37 -06:00
nm-device-bond.xml \
bridge: add bridge device type This adds a new device type 'bridge'. Kernel devices are created on demand.
2012-10-29 19:02:45 -05:00
nm-device-bridge.xml \
core: convert VLAN interfaces to a device subclass Many different interface types can support VLANs, including Infiniband, WiFi, etc. So we have to create a new device class for them instead of keeping the support in NMDeviceEthernet.
2012-02-22 23:59:50 -06:00
nm-device-vlan.xml \
core, libnm-glib: add NMDeviceGeneric Add NMDeviceGeneric, to provide generic support for unknown device types, and create NMDeviceGenerics for those devices that NM previously was ignoring. Allow NMSettingGeneric connections to be activated on (managed) NMDeviceGenerics.
2013-04-17 10:41:15 -04:00
nm-device-generic.xml \
Add missing introspection files to tarball (Robert Piasek) git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@4023 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-28 14:12:09 +00:00
nm-device.xml \
nm-ip4-config.xml \
ipv6: fix missing introspection file in distcheck
2009-08-04 14:55:22 -04:00
nm-ip6-config.xml \
Add missing introspection files to tarball (Robert Piasek) git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@4023 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-28 14:12:09 +00:00
nm-manager.xml \
nm-settings.xml \
core: rename NMSysconfigConnection -> NMSettingsConnection
2011-01-26 11:38:12 -06:00
nm-settings-connection.xml \
Add missing introspection files to tarball (Robert Piasek) git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@4023 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-08-28 14:12:09 +00:00
nm-vpn-plugin.xml \
nm-vpn-connection.xml \
2008-03-20 Dan Williams <dcbw@redhat.com> * introspection/nm-manager.xml introspection/nm-manager-client.xml - (ActivateConnection): return the object path of the active connection on success - (GetActiveConnections): remove - (DeactivateConnection): new function; deactivate a currently active connection - Add an ActiveConnections property which returns an array of active connection object paths * introspection/nm-device.xml - (Deactivate): remove * introspection/all.xml - Add ActiveConnection introspection * introspection/nm-active-connection.xml - Add the ActiveConnection object * include/NetworkManager.h - Add the Connection.Active D-Bus interface * src/nm-device-interface.c - (impl_device_deactivate): remove * src/nm-activation-request.c src/nm-activation-request.c src/Makefile.am - Implement the Connection.Active D-Bus interface * src/nm-manager.c - (get_property, nm_manager_class_init): add ACTIVE_CONNECTIONS property - (nm_manager_activate_device): return the active connection path - (connection_added_default_handler, impl_manager_activate_connection): return the active connection to the caller - (add_one_connection_element, impl_manager_get_active_connections): remove - (impl_manager_deactivate_connection): new function; deactivate an active connection * libnm-glib/nm-device.c libnm-glib/nm-device.h - Remove Deactivate() function git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3484 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-03-20 19:56:12 +00:00
nm-ppp-manager.xml \
2008-07-17 Dan Williams <dcbw@redhat.com> * introspection/Makefile.am introspection/nm-device.xml introspection/nm-dhcp4-config.xml - Add bits for the DHCP4Config property of the device, and the DHCP4Config itself * src/nm-device-interface.c src/nm-device-interface.h - Add the DHCP4Config property * src/nm-device.c - Keep track of DHCP4 options via a new DHCP4Config property and notify D-Bus clients when it changes * src/nm-dhcp4-config.c src/nm-dhcp4-config.h - Simple object to store DHCP4 options, export them over D-Bus, and notify when they change * src/dhcp-manager/nm-dhcp-manager.c src/dhcp-manager/nm-dhcp-manager.h - (nm_dhcp_manager_set_dhcp4_config, copy_dhcp4_config_option): copy and filter server-returned DHCP options into an NMDHCP4Config object git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3829 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2008-07-17 17:04:13 +00:00
nm-active-connection.xml \
dhcp: add the NMDHCP6Config object
2010-01-13 22:30:40 -08:00
nm-dhcp4-config.xml \
agent: add agent manager and minimal agent class
2010-12-10 12:38:19 -06:00
nm-dhcp6-config.xml \
Merge remote branch 'origin/master' into rm-userset
2011-01-12 15:46:37 -06:00
nm-agent-manager.xml \
build: make sure nm-secret-agent.xml gets into the tarball
2011-02-02 21:39:03 -06:00
nm-wimax-nsp.xml \
nm-secret-agent.xml
Fix distcheck git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@2831 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2007-09-20 11:37:14 +00:00
Reference in a new issue Copy permalink