Age | Commit message (Collapse) | Author | Files | Lines |
|
Unfortunately we cannot fully remove the blacklist name forever, as we
must keep API. We move it to -compat so that it gets removed whenever
we decide to break API.
|
|
|
|
This CID is used by host to query the modem for its wake reason when
power up because of device wake. If the device supports this function,
but fails the query from host, it means the power up is not caused by
a wake from the device.
Includes updates by Aleksander Morgado to fix coding style issues,
message definitions add missing documentation items.
|
|
This CID is used to notify the host of the configuration progress and
parameters of the device. This CID is added as part of MBIM 3.0
extension.
Includes updates by Aleksander Morgado to fix coding style issues,
memory handling fixes add missing documentation items.
|
|
This is a TLV that contains an array of guint16 values. For now we
only add reading support,
|
|
The type is introduced in MBIMEx v3.0, so just name it with the v3
suffix, not to confuse with the updated introduced in MBIMEx v2.0,
which is compatible with the original type in MBIM v1.0.
|
|
|
|
The Microsoft Extensions define a new generic TLV type that allows
including any kind of data in it: from strings, to arrays of uints, to
more complex types.
We define support for the generic 'tlv' type and the generic
'tlv-list' type, which allow implementing the "unnamed IEs" that are
appended to some new messages in the MS extensions.
And we also define support for a more specific 'tlv-string', used
exclusively when the TLVs are part of the named fields, so that we can
provide strings in our libmbim-glib APIs, instead of requiring the
user to build MbimTlv instances.
|
|
|
|
There are service updates that will re-use parts of the previous
versions of the same service (e.g. struct types and such). In order to
provide an easy way to reference all those common types among versions
of the same service, we'll just build all of them together in the same
source files.
|
|
Value 0 in the MbimNwError field reports no error, not an unknown
error.
We provide a compat symbol to avoid breaking API.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This command is an extension for the existing MBIM_CID_PACKET_SERVICE
defined in the MBIM specification revision 1.0. This extension adds a
new member called FrequencyRange for the response structure and
renamed the HighestAvailableDataClass member to CurrentDataClass to
clarify its purpose.
|
|
message
This service specifies new versions of the messages (API breaks) in
the generic Basic Connect service, and therefore it reuses the same
service UUID and message CID definitions as in the original Basic
Connect service.
Only the 'Register State' message support is implemented at this
stage.
|
|
The exchange of the MBIMEx version to use between host and device is
exclusively done via the MBIM_DEVICE_OPEN_FLAGS_MS_MBIMEX_V2 flag in
the mbim_device_open_full() request. Once this request finishes, the
device instance will know which is the MBIMEx version agreed, and the
user can gather this same information with the new version getter
method.
In addition to the version getter, a simple version checker method is
also implemented, which allows users of the API to quickly check
whether the agreed version is equal or greater than the given one, and
this helps writing clear code doing the checks.
A new setter method is also provided for the device object, which is
supposed to be used when the user already knows which specific version
has been agreed between host and device. The setter doesn't do any
MBIM interaction with the real device, it just updates its internal
records of which the current MBIMEx version is.
|
|
Although not totally necessary due to its implementation, some files
built by meson are included as content files.
They have been explicitly added for the sake of correctness.
|
|
meson gained the dictionaries as builtin objects[0] that can be
modified with the addition operator[1] and can be useful when
setting configuration or even environment values[2].
The individual object creation has been replaced by dictionaries
when possible.
[0] http://mesonbuild.com/Release-notes-for-0-47-0.html#new-builtin-object-type-dictionary
[1] https://mesonbuild.com/Release-notes-for-0-48-0.html#dictionary-addition
[2] https://mesonbuild.com/Release-notes-for-0-52-0.html#support-taking-environment-values-from-a-dictionary
|
|
Since meson 0.49, the `/` character can be used to join paths[0], so
all the instances of `join_paths` have been replaced.
[0] http://mesonbuild.com/Release-notes-for-0-49-0.html#joining-paths-with-
|
|
A new variable called `mbim_name` has been created to avoid the call
to a function inside the meson object.
|
|
To avoid the burden of maintaining multiple build systems, autotools
support has been removed.
Fixes #18.
|
|
There is no such license as GPL-2 in the SPDX nomenclature. As
the project is licensed under GNU General Public License v2.0
or later, use the related identifier GPL-2.0-or-later.
|
|
|
|
MSFT MBIM_CID_MS_UICC_RESET is used to reset the UICC or
to query passthrough state of the function.
If host/application specifies passthrough action, the function
resets the UICC and upon UICC power up, treats the UICC as if
it were in a passthrough mode. If the passthrough action is
disabled during reset operation then upon power up, treats
the UICC as a regular Telecom UICC and expects a Telecom
UICC file system to be present on the UICC
|
|
MSFT MBIM_CID_MS_UICC_APDU is used to send a command APDU to
a specific logical channel on the UICC and receive the
response. Sending entity has to ensure that the logical
channel was previously opened with uicc-open channel.
Refer section 10.1.1 of ETSI TS 102 221 TS for more details
on apdu encoding/decoding.
|
|
The Answer to Reset(ATR) CID implementation.
ATR is the first string of bytes sent by the UICC after
reset has been performed. Host should save this ATR when
it is received from UICC for future use.
|
|
We query device slot information status and we can see
the following information.
mbimcli -d /dev/cdc-wdm0 -p --ms-query-slot-info-status=1
[/dev/cdc-wdm0] Slot info status retrieved:
SLot 1: slot-state-active
|
|
The "LTE Attach Status" message was relying on a bogus
MbimLteAttachStatus struct that was created by the library and passed
as output of the parser methods to the user.
This struct is completely avoidable, just by updating the messages to
include the fields directly in the response/notification fields.
We rename the method to 'LTE attach info' following this approach, and
compatibility symbols are included in order to avoid breaking API/ABI.
|
|
meson is a build system focused on speed an ease of use, which
helps speeding up the software development. This patch adds meson
support along autotools.
|
|
|
|
QDU (Qualcomm Device Upgrade) is required for Qualcomm modem
firmware upgrade.
Signed-off-by: lywpljw <327669727@qq.com>
|
|
|
|
|
|
We rely on sysfs to tell us which links a given network interface
already has.
|
|
The MBIM devices support multiplexing as part of the protocol itself,
and in the cdc_mbim driver this feature has been supported from the
very first version of the driver.
In the cdc_mbim driver, MBIM IP sessions are mapped to VLAN IDs
matching the MBIM session IDs, and so we can use netlink operations to
request adding or removing links as appropriate.
This operation is completely equivalent to the link management
operations done in libqmi when using RMNET, so the new net port
manager internal object running the netlink operations is highly based
on the QmiNetPortManagerRmnet class defined in libqmi-glib.
Unlike in the libqmi case, there are no other supported net link
management backends, just one, so the MbimNetPortManager is not an
abstract class, it is instead the class implementing support for the
single cdc_mbim backend.
|
|
Instead of having them listed in the installed mbim-utils.h
|
|
|
|
|
|
|
|
|
|
For now just with the "Config" message, and mbimcli query support.
|
|
The .actions file is generated by newer gtk-doc releases, we just
treat it as e.g. the .signals or .types files.
This is also already fixed in upstream gtk-doc:
https://gitlab.gnome.org/GNOME/gtk-doc/-/merge_requests/61
|
|
(cherry picked from commit 2f870ec400c4c12513d809eccde1da34e80f7d9f)
|
|
|
|
|
|
|