Age | Commit message (Collapse) | Author | |
---|---|---|---|
2012-08-28 | qmi-bearer: use new enum types for call end reasonsqmi-support | Aleksander Morgado | |
Sync with libqmi: commit d473f9ab35b85b76ebd6510a69a49ffa141d85f1 Author: Aleksander Morgado <aleksander@lanedo.com> Date: Tue Aug 28 13:18:44 2012 +0200 wds: implement "Verbose Call End Reason" types commit d39c997771da9a8037e61f1b4fc5ccfbb34be952 Author: Aleksander Morgado <aleksander@lanedo.com> Date: Mon Aug 27 20:29:16 2012 +0200 wds: implement "Call End Reason" type | |||
2012-08-28 | qmi-bearer: fix IPv6 disconnection logic | Aleksander Morgado | |
2012-08-27 | bearer-qmi: only keep internal state if IP type specific connection succeeds | Aleksander Morgado | |
2012-08-27 | bearer-qmi: if possible, use "WDS Set IP Family" to select IP family preference | Aleksander Morgado | |
2012-08-27 | bearer-qmi: only specify IP family preference TLV if one explicitly requested | Aleksander Morgado | |
2012-08-27 | bearer-qmi: allocate different WDS clients for IPv4 and IPv6 setups | Aleksander Morgado | |
2012-08-27 | qmi-port: allow allocating more than one client of a given service | Aleksander Morgado | |
We'll uniquely identify each client generated by the service ID and a user defined flag, so that we then allow to peek/get the specific client. | |||
2012-08-27 | bearer-qmi: enable dual IPv4/IPv6 connections | Aleksander Morgado | |
We provide separate steps to connect/disconnect IPv4 and IPv6. | |||
2012-08-24 | bearer-qmi: make compiler happy | Aleksander Morgado | |
2012-08-23 | bearer-qmi: 'no-effect' errors while starting network aren't fatal | Aleksander Morgado | |
2012-08-23 | bearer-qmi: pass down APN/username/password/IP-type to `WDS Start Network' | Aleksander Morgado | |
2012-08-23 | bearer-qmi: implement connection/disconnection sequences | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: create a `MMBearerQmi' always by default | Aleksander Morgado | |
We still don't consider the case of having all net ports already connected and falling back to PPP over a serial port. | |||
2012-08-23 | bearer-qmi: new `MMBearerQmi' object | Aleksander Morgado | |
This bearer type does not inherit from `MMBroadbandBearer', and therefore it doesn't need to be async-initable. | |||
2012-08-23 | build: minor reorder of files to build | Aleksander Morgado | |
2012-08-23 | broadband-bearer: remove obsolete property names | Aleksander Morgado | |
2012-08-23 | iface-modem: max number of bearers equal to the number of available data ports | Aleksander Morgado | |
2012-08-23 | base-modem: allow getting/peeking all data ports | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: assume we don't have messaging support | Aleksander Morgado | |
Just to cleanup the sequence for now, we can develop it later. | |||
2012-08-23 | broadband-modem-qmi: assume we don't have USSD support | Aleksander Morgado | |
Just to cleanup the sequence for now, we can develop it later. | |||
2012-08-23 | core: handle the 'usb'->'usbmisc' subsystem rename in the kernel | Aleksander Morgado | |
We'll try to cope with getting devices being reported in either 'usb' or 'usbmisc', trying to avoid the need of checking kernel version during runtime. | |||
2012-08-23 | broadband-modem-qmi: don't allocate WDS client during startup | Aleksander Morgado | |
We'll allocate WDS clients only when launching a connection. | |||
2012-08-23 | base-modem: allow grabbing multiple 'net' and 'qmi' ports | Aleksander Morgado | |
All grabbed 'net' ports are added to the new list of data ports. It is a task for the specific plugin to decide how each of the data ports should be connected. In the case of not having 'net' ports, the list of data ports will only contain a single AT port. All grabbed 'qmi' ports are added to the new list of QMI ports. The first port in the list is to be considered the 'primary' one, and will be the one used for all services. The remaining QMI ports, if any, will only be used to for WDS, to manage the associated 'net' ports. | |||
2012-08-23 | broadband-modem-qmi: don't rely on the detailed service status to get HDR reg | Aleksander Morgado | |
The 'detailed service status' TLV is either pretty new and not always available, or given only under some specific circumstances. So, try to gather CDMA1x and EV-DO registration status with the default info we usually do get. The logic is the following: * If registered and the access technologies contain CDMA1x, then CDMA1x is registered, otherwise it's not. * If registered and the access technologies contain any of the EV-DO revisions, then EV-DO is registered, otherwise it's not. An example output in a CDMA network: [/dev/cdc-wdm0] Successfully got serving system: Registration state: 'registered' CS: 'attached' PS: 'attached' Selected network: '3gpp2' Radio interfaces: '2' [0]: 'cdma-1xevdo' [1]: 'cdma-1x' Roaming status: 'off' Data service capabilities: '2' [0]: 'cdma' [1]: 'evdo-rev-a' Current PLMN: MCC: '311' MNC: '480' Description: 'Verizon Wireless' CDMA System ID: SID: '26' ESN: '1' CDMA Base station info: Base station ID: '3633' Latitude: '44.913333'º Longitude: '-93.279722'º Roaming indicators: '2' [0]: '(null)' (cdma-1x) [1]: '(null)' (none) Default roaming status: '(null)' 3GPP2 time zone: Leap seconds: '16' seconds Local time offset: '-300' minutes Daylight saving time: 'no' CDMA P_Rev: '6' | |||
2012-08-23 | broadband-modem-qmi: handle serving system output when selected network is ↵ | Aleksander Morgado | |
unknown Seems that sometimes we get 'selected network' as UNKNOWN, but we still have proper registration information. Try to handle those cases. [/dev/cdc-wdm0] Successfully got serving system: Registration state: 'registered' CS: 'detached' PS: 'attached' Selected network: 'unknown' Radio interfaces: '1' [0]: 'lte' Roaming status: 'off' Data service capabilities: '1' [0]: 'lte' Current PLMN: MCC: '311' MNC: '480' Description: 'Verizon Wireless' Roaming indicators: '1' [0]: 'off' (lte) | |||
2012-08-23 | broadband-modem-qmi: use only deprecated commands | Aleksander Morgado | |
The QMI protocol is updated frequently with new commands replacing and improving some already existing ones, which get marked as deprecated. Instead of initially try to cover the logic with both the old and the new commands, we'll default to use only the old deprecated ones, which should be supported also in the modems with newer services. The supported already implemented for the new QMI commands is hidden behind a `--with-newest-qmi-commands' configure switch. Once the implementation is fully developed and tested using the deprecated commands we can then focus in including the support for the new ones. | |||
2012-08-23 | broadband-modem-qmi: implement supported modes loading | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: implement CDMA unsolicited registration events for NAS ↵ | Aleksander Morgado | |
< 1.8 | |||
2012-08-23 | broadband-modem-qmi: implement CDMA registration checks for NAS < 1.8 | Aleksander Morgado | |
2012-08-23 | iface-modem-cdma: provide separate method to update access tech | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: build 3GPP access technologies from data service ↵ | Aleksander Morgado | |
capabilities | |||
2012-08-23 | iface-modem-3gpp: provide separate methods to update access tech and location | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: include '3gpp' prefix in the 3GPP registration checks | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: don't keep cs|ps flags when checking registration status | Aleksander Morgado | |
Just report both always. | |||
2012-08-23 | iface-modem-3gpp: log about which registration check will be run | Aleksander Morgado | |
2012-08-23 | iface-modem-cdma: allow implementations to fully override registration checks | Aleksander Morgado | |
Implementations of the CDMA interface can either: * Implement run_registration_checks() or, * Implement the sub-steps of the generic registration checks sequence | |||
2012-08-23 | Revert "iface-modem-cdma: ease the logic for plugins providing only detailed ↵ | Aleksander Morgado | |
reg info" This reverts commit 3661c9ed847be490f9034b41d3b035cab1cf78de. | |||
2012-08-23 | iface-modem-cdma: minor fix in interface API names | Aleksander Morgado | |
2012-08-23 | iface-modem-cdma: ease the logic for plugins providing only detailed reg info | Aleksander Morgado | |
2012-08-23 | TODO: QMI based modems always require a QMI and WWAN port | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: 'no-effect' is not an error during automatic registration | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: fix signal handlers | Aleksander Morgado | |
User data is always the last parameter | |||
2012-08-23 | broadband-modem-qmi: implement auto/manual network registration using QMI | Aleksander Morgado | |
2012-08-23 | iface-modem-3gpp: implement the network registration request logic | Aleksander Morgado | |
In the generic broadband modem implementation we'll just implement the specific command to request auto/manual network registration, and we leave all the other logic (waiting for the new registration status and all that) in the interface, as it is really common for every possible implementation. | |||
2012-08-23 | broadband-modem: validate operator ID before trying to register to it | Aleksander Morgado | |
2012-08-23 | modem-helpers: new method to validate and/or parse MCC/MNC operator ID string | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: limit 3GPP registration updates for 3GPP modems | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: consolidate Serving System response/indication processing | Aleksander Morgado | |
2012-08-23 | broadband-modem-qmi: implement 3GPP unsolicited registration events for NAS ↵ | Aleksander Morgado | |
>= 1.8 | |||
2012-08-23 | TODO: add note about SIM provisioning info | Aleksander Morgado | |