Age | Commit message (Collapse) | Author |
|
The 1.24.0 stable release can be used as minimum requirement for the
new ModemManager 1.12.0 release.
|
|
Based on:
$ git shortlog -s -n
|
|
|
|
|
|
Since this plugin uses a bitmask to represent bands, we have
to be wary of shifting outside the precision of the bitmask
storage type. In this case, it was possible to generate 1 << 31
in a signed integer type as an intermediate step of B3G_FLAG,
which is undefined behavior (and usually results in INT_MIN,
breaking comparisons with the value).
Bug was reported to the chromium tracker at crbug.com/1019301
Original patch updated by Aleksander Morgado to leave
MM_MODEM_BAND_TELIT_3G_LAST as MM_MODEM_BAND_UTRAN_19, as that is the
highest 3G band supported by the current implementation. Worth noting
that this was not a real bug as the maximum flag we would have been
setting was (1 << 19) anyway.
|
|
We would have been de-referencing a NULL GError.
|
|
|
|
|
|
Signed-off-by: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
|
|
Signed-off-by: Sven Schwermer <sven.schwermer@disruptive-technologies.com>
|
|
Use g_list_free_full() using g_object_unref() as #GDestroyNotify
function instead.
|
|
So that the GI scanner ignores them.
|
|
This property was already deprecated in libmm-glib and removed from
the daemon in 1.10, so the counterpart property in MMSimpleStatus
should also be deprecated.
|
|
|
|
There is absolutely no reason to provide any other property when the
user creates a new call.
|
|
|
|
Use <chapter> so that all per-version indices are included in the docs.
|
|
This method is used by the daemon to modify the GList of MMPco
objects, the client should not need to use this method for anything.
|
|
G_MINDOUBLE is 0.0, which is a valid altitude, latitude, and
longitude. Change the 'unknown' location values to -G_MAXDOUBLE
instead, which is a completely invalid value in all cases.
This is strictly an ABI break, but it's also true that until now the
methods returning these 'unknown' values could also return valid 0.0
values that would have been detected as 'unknown' by the caller.
So, just stop this madness and don't consider this any ABI break.
This is the same thing we had to do with MM_SIGNAL_UNKNOWN in
fe66bdf65e57fa7dee3dcb8dea068fb3fc7aec34.
|
|
The extra character size was only being applied when > 10 elements,
leaving the == 10 case out of it, so the output was being truncated.
Fix it, by using a more generic way to computing how many extra
characters we need in the size.
Fixes https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/151
|
|
methods
|
|
We just move the MM_DISABLE_DEPRECATED check to after the
MM_DEPRECATED symbol definition, because gtkdoc-scan gets pretty
confused, likely due to the symbol ending with the "_DEPRECATED"
suffix.
Fixes https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/91
|
|
|
|
|
|
DOC Building HTML
Element term in namespace '' encountered in para, but no template matches.
DOC Fixing cross-references
|
|
|
|
|
|
It was observed that sporadically it may take more than 5 seconds for modem to
respond to AT#REBOOT. Increase the timeout on AT command to not report
unnecessary errors to the user.
|
|
|
|
|
|
|
|
|
|
The result of these commands may be different before and after SIM-PIN
unlock, so never cache them.
|
|
The supported voice features may be different before and after SIM-PIN
unlock, so do not cache the result of the support check operation.
|
|
The result of these commands may be different before and after SIM-PIN
unlock, so never cache them.
|
|
|
|
If we get one of the in-call termination errors before ATD replies OK,
we need to cancel the start() operation right away and return an
error to the caller.
Otherwise, the Call will be reported as "terminated" right away, but
the caller would not get an error back until 90s later:
$ sudo mmcli --call 0 --start
error: couldn't start the call: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Serial.ResponseTimeout: Serial command timed out'
|
|
This is so that we can receive and process URCs even if the modem is
not fully enabled yet.
|
|
|
|
Used during initialization, enabling and sim hotswap context setup.
The secondary AT and QCDM ports will only be open during enabling.
|
|
These are already given in the logic behind the
"MM_PORT_SERIAL_AT_INIT_SEQUENCE" property:
(ttyACM1): --> 'ATE0<CR>'
(ttyACM1): <-- '<CR><LF>OK<CR><LF>'
(ttyACM1): --> 'ATV1<CR>'
(ttyACM1): <-- '<CR><LF>OK<CR><LF>'
(ttyACM1): --> 'AT+CMEE=1<CR>'
(ttyACM1): <-- '<CR><LF>OK<CR><LF>'
(ttyACM1): --> 'ATX4<CR>'
(ttyACM1): <-- '<CR><LF>OK<CR><LF>'
(ttyACM1): --> 'AT&C1<CR>'
(ttyACM1): <-- '<CR><LF>OK<CR><LF>'
(ttyACM1): --> 'ATE0<CR>' --> redundant
(ttyACM1): <-- '<CR><LF>OK<CR><LF>'
(ttyACM1): --> 'AT+CMEE=1<CR>' --> redundant
(ttyACM1): <-- '<CR><LF>OK<CR><LF>'
|
|
This new flag allows users of the API to know whether general purpose
voice calls are allowed or otherwise only voice calls to the
registered emergency numbers should be performed.
ModemManager won't really do any distinction between emergency and
non-emergency calls at this point, this flag is just an early
indication for the user of the API that no normal voice call should be
attempted.
|
|
|
|
We're going to allow emergency calls at any point, so prepare the call
list handling logic during initialization, not when the modem is first
enabled.
|
|
|
|
Instead of using the firmware step as fallback when the modem goes
into failed or locked state, use an independent step in the
initialization state machine, just to make it clearer.
|
|
We only allow one single Simple.Connect() attempt at a time. If more
than one arrives, the second and next ones will be forbidden.
The ongoing connection attempt can now always be cancelled via
Simple.Disconnect(), not only *after* the bearer object connection has
started. i.e. if Simple.Disconnect() is called e.g. while waiting to
be registered, we would also be cancelled properly.
|
|
|
|
As discussed in https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/130
Fixes https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/130
Fixes https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/129
|
|
|