aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2013-03-27broadband-modem-sierra: fix trivial copy & paste errorDan Williams
2013-03-27broadband-modem: prefer specific access tech checks over generic +CGREG ↵Dan Williams
access tech (bgo #696705) If the modem has specific access technology checks, don't override them with the generic access technology from +CGREG responses, since that doesn't have the granularity that specific checks do. For example, the +CGREG response only indicates UMTS, and cannot indicate HSDPA, HSUPA, HSPA, HSPA+, DC-HSPA, etc.
2013-03-27broadband-modem: remove debugging codeDan Williams
Slipped in while debugging Nozomi stuff; not caught in review.
2013-03-27iface-modem: never try to create a SIM in a CDMA-only modemAleksander Morgado
CDMA modems without LTE capabilities will usually not have a SIM, so just skip loading a SIM object if so. https://bugzilla.gnome.org/show_bug.cgi?id=696582
2013-03-27broadband-modem-qmi: zero-pad ESN to 8 charactersDan Williams
It's very likely to already be 8 characters, but if by some chance it's 7, zero-pad like we do for AT+GSN responses in the generic CDMA code.
2013-03-27broadband-modem: parse +GSN response for IMEI, MEID, and ESN (bgo #696596)Dan Williams
+GSN response differs widely between modems. Some prefix the MEID and/or ESN with 0x, some have leading zeros, some return the MEID and the ESN, and some append the serial number to the end of the IMEI. Handle that and make the ESN, MEID, IMEI, and EquipmentIdentifier parsing consistent.
2013-03-26sms-part: use correct printf modifier for gsizeAleksander Morgado
This is the port to git master of the following commit: commit 294a91d9f6390d532399be35ddbf6a2b8d136576 Author: Thomas Bechtold <thomasbechtold@jpberlin.de> Date: Mon Mar 25 14:28:03 2013 +0100 sms-utils: use correct printf modifier for gsize
2013-03-25broadband-modem: minimally verify QCDM MDN before using itDan Williams
Sometimes it's garbage, and we don't like garbage.
2013-03-25broadband-modem-sierra: add after-sim-unlock delayDan Williams
Older devices may crash if asked to connect right after sending the PIN and unlocking the SIM; they simply stop responding to AT commands around the first request for access technology and then reboot. A delay seems prevents this behavior. Since it's not uncommon to require a delay after SIM unlock, add one for newer sierra_net devices as well, even though we're not quite sure if they need one or not. It doesn't hurt, at least.
2013-03-25sierra: fix time check warnings for modems that don't support timeDan Williams
'result' may be NULL even if no error is set. Errors aren't set because we want to continue the !TIME/!SYSTIME sequence regardless of errors, so we can figure out which command the modem supports. Trying to get a uint32 out of a NULL GVariant makes glib complain, and it's wrong, so don't do that.
2013-03-22iface-modem-cdma: fix use of uninitialized variableAleksander Morgado
2013-03-22cli: show CDMA activation state infoAleksander Morgado
2013-03-22broadband-modem-qmi: implement automatic CDMA activationAleksander Morgado
2013-03-22broadband-modem-qmi: new generic power cycle actionAleksander Morgado
2013-03-22broadband-modem-qmi: implement initial CDMA activation state loadingAleksander Morgado
2013-03-22iface-modem-cdma: load initial activation state during initAleksander Morgado
2013-03-22iface-modem-cdma: allow reporting activation state changesAleksander Morgado
2013-03-22api,enums: new `MM_MODEM_CDMA_ACTIVATION_STATE_UNKNOWN' valueAleksander Morgado
Used initially when we don't know the current activation state.
2013-03-22api,introspection: new `ActivationState' property in the CDMA interfaceAleksander Morgado
2013-03-22api,introspection: minor updates in the CDMA interface descriptionsAleksander Morgado
2013-03-21bearer-qmi: don't try to gather connection settings if we didn't connectAleksander Morgado
2013-03-20blacklist: ignore Arduino devicesAleksander Morgado
https://bugs.launchpad.net/bugs/910736 https://bugs.launchpad.net/bugs/1153632
2013-03-20error-helpers: avoid crash when error is not recognizedAleksander Morgado
Just remove the last element with NULL strings in the array of errors, as we're safe using G_N_ELEMENTS() to iterate it. Reported by Jose Maria Gonzalez Calabozo <jmgonzalezc@indra.es>
2013-03-20iface-modem-cdma: fix checking support for manual activationAleksander Morgado
2013-03-14build: fix check for libqmi when newest QMI commands are enabledAleksander Morgado
Reported by Marius Kotsbak <marius.kotsbak@gmail.com>
2013-03-13blacklist: ignore West Mountain radio devicesAleksander Morgado
https://bugs.launchpad.net/bugs/1154654
2013-03-13qcdm: add auto-LTE modes for GSM and CDMADan Williams
as in, CDMA+EVDO+LTE and GSM+UMTS+LTE which were missing before.
2013-03-13build: ignore 'modepref' testAleksander Morgado
2013-03-12qcdm: modepref: reset device after setting mode preferenceDan Williams
Otherwise it doesn't actually take until you unplug/replug.
2013-03-12build: distribute autogen.shDan Williams
2013-03-12qcdm: add modepref utilityDan Williams
Sets and gets the NV "mode pref" item for allowed access technologies.
2013-03-12qcdm: fix up NV Mode Pref item handlingDan Williams
While the QCDM and DIAG_NV are the same, in reality they shouldn't be and there should be a mapping between them. That wasn't happening, so fix that up and add a few missing modes to the NV item defines.
2013-03-12wmc: add get functionality to uml290modeDan Williams
2013-03-12broadband-modem-qmi: fix logic to include GSM/WCDM acquisition order preferenceAleksander Morgado
2013-03-12zte: add port type hints for the ZTE MF195Aleksander Morgado
https://bugzilla.gnome.org/show_bug.cgi?id=691480
2013-03-12modem-helpers-qmi: fix allowed mode translation from QMI to MMAleksander Morgado
Which actually fixes allowed mode switching in MM...
2013-03-12broadband-modem-qmi: fix initial operating mode loadingAleksander Morgado
2013-03-12broadband-modem-qmi: handle 'UimUninitialized' error when checking unlock statusAleksander Morgado
QMI modems without SIM may report 'UimUninitialized' QMI protocol errors, so catch those and use them as 'SIM failure' so that they get reported to the user.
2013-03-06broadband-modem: fix enable flag in UnsolicitedRegistrationEventsContextBen Chan
2013-03-05mbm: fix 3gpp dialling sequence when result comes through pollingAleksander Morgado
2013-03-05mbm: tag the ttys instead of the parent usb deviceAleksander Morgado
We can just tag the ttys instead of the parent usb device, so that the core logic which looks in the plugin-specified port tags works properly. There is no need to explicitly tag the net port, as the probing for this port ends when a plugin suggestion comes from another port probing on the same device.
2013-03-05udev: tag all devices from idVendor 0x0711 as manual-scan-onlyAleksander Morgado
Magic Control Technology Corp (0x0711) manufacturers several USB<->RS232 adapters.
2013-03-05core: don't automatically probe ports of USB<->serial adaptersAleksander Morgado
We should not automatically probe ports marked as coming from USB to serial adapters, as we're not sure that a modem is behind the adapter. Still, let the user request a manual scan and have these devices probed in that case. https://bugzilla.gnome.org/show_bug.cgi?id=647556 https://bugzilla.gnome.org/show_bug.cgi?id=691076
2013-03-05iface-modem-3gpp: handle non-deferrable registration state updatesBen Chan
This patch changes MMIfaceModem3gpp to differentiate between deferrable and non-deferrable 3GPP registration state updates. Periodic or unsolicited registration state updates are deferrable, while internal updates, e.g. due to modem being disabled, are non-deferrable.
2013-03-05broadband-modem: fix disabling of unsolicited registration eventsBen Chan
2013-03-04sierra: add MC8790 to APP1 PPP whitelistGerald Richter
2013-03-01iface-modem-3gpp: avoid re-setting deferred registration update while disablingAleksander Morgado
Don't clear the current deferred registration update until having disabled and cleaned up unsolicited registrations state messages, or we may end up re-setting the deferred registration update again meanwhile
2013-03-01iface-modem-3gpp: clear deferred registration state update when disablingBen Chan
2013-02-26udev: update all udev rules to always match both VID/PID togetherAleksander Morgado
If the rules to tag specific USB interface numbers only apply on the PID, we'll end up seeing that if the port has a parent with another PID, and that other PID also has a rule, port will get tagged multiple times. Easier to see with an example: The ZTE MF637 (VID 0x19D2, PID 0x0121) had the following rules: ATTRS{idProduct}=="0121", ENV{.MM_USBIFNUM}=="04", ENV{ID_MM_ZTE_PORT_TYPE_MODEM}="1" ATTRS{idProduct}=="0121", ENV{.MM_USBIFNUM}=="01", ENV{ID_MM_ZTE_PORT_TYPE_AUX}="1" In our ZTE rules we also have some for the device with PID 0x0002, like: ATTRS{idProduct}=="0002", ENV{.MM_USBIFNUM}=="02", ENV{ID_MM_ZTE_PORT_TYPE_MODEM}="1" ATTRS{idProduct}=="0002", ENV{.MM_USBIFNUM}=="04", ENV{ID_MM_ZTE_PORT_TYPE_AUX}="1" And it seems that we can grab multiple PIDs from a single port, i.e. from the parent objects in the hierarchy: udevadm info -a -n /dev/ttyUSB4 | grep idProduct ATTRS{idProduct}=="0121" ATTRS{idProduct}=="0020" ATTRS{idProduct}=="0002" Where that 0x0002 idProduct is not from the modem, but from the EHCI Host Controller (with idVendor 0x1d6b in my case). So... we end up seeing that both set of rules will apply to the ports, and we misleadingly get: (ttyUSB3) type 'at' claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ZTE: AT port 'tty/ttyUSB2' flagged as primary (ttyUSB2) type 'at' claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ZTE: AT port 'tty/ttyUSB1' flagged as secondary (ttyUSB1) type 'at' claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ZTE: AT port 'tty/ttyUSB4' flagged as primary b_port(): (ttyUSB4) type 'at' claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 (/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2) tty/ttyUSB2 at (primary) (/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2) tty/ttyUSB1 at (secondary) (/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2) tty/ttyUSB2 data (primary) (/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2) tty/ttyUSB0 qcdm Which is wrong, as ttyUSB4 should have been our primary port, not ttyUSB2. With this patch on, the rules apply only to the VID/PID pair, and we end up getting what we really wanted: (ttyUSB3) type 'at' claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 (ttyUSB2) type 'at' claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ZTE: AT port 'tty/ttyUSB1' flagged as secondary (ttyUSB1) type 'at' claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 ZTE: AT port 'tty/ttyUSB4' flagged as primary b_port(): (ttyUSB4) type 'at' claimed by /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2 (/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2) tty/ttyUSB4 at (primary) (/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2) tty/ttyUSB1 at (secondary) (/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2) tty/ttyUSB4 data (primary) (/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2) tty/ttyUSB0 qcdm https://bugzilla.gnome.org/show_bug.cgi?id=694759
2013-02-26iface-modem: allow falling back to 'failed' stateAleksander Morgado
Allow mm_iface_modem_update_state() receive 'MM_MODEM_STATE_FAILED', and treat it as any other change to failed state, but with 'MM_MODEM_STATE_FAILED_REASON_UNKNOWN'.
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2025-06-08 11:15:25 +0000