| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Initially, load sysfs path and setup state machine.
|
| |
|
|
|
|
|
| |
We want to start using new GLib features like e.g. GTask, available in
GLib 2.36.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
If libmbim 1.14.0 found, enable QMI over MBIM support.
|
|
|
|
| |
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
| |
|
| |
|
|
|
|
|
| |
This is not an official release, just an easy way to identify when the new
support for the UIM PIN actions was introduced.
|
|
|
|
|
| |
This is not an official release, just an easy way to identify when the new
support for the 'kernel expected data format' getter/setter were introduced.
|
|
|
|
|
| |
Also, version bump to 1.13.5 to flag the exact version in which the change was
introduced.
|
|
|
|
|
| |
Not an official release, just a way to flag the availability of the new "DMS
Set FCC Authentication" command.
|
|
|
|
|
|
|
| |
Just a enum value rename, but breaks API.
Also, version bump to 0.13.3 to flag the exact version in which the change
was introduced.
|
|
|
|
|
|
|
|
|
|
|
|
| |
ECIO List TLV (0x12) in the NAS Get Signal Strength response message is given as an
unsigned byte, representing negative 0.5dB increments.
This is an API break; added to NEWS already not to forget about it.
Also, version bump to 0.13.2 to flag the exact version in which the change
was introduced.
https://bugs.freedesktop.org/show_bug.cgi?id=85052
|
|
|
|
|
|
|
|
|
|
|
|
| |
ECIO TLV (0x14) in the NAS Event Report Indication message is given as an
unsigned byte, representing negative 0.5dB increments.
This is an API break; added to NEWS already not to forget about it.
Also, version bump to 0.13.1 to flag the exact version in which the change
was introduced.
https://bugs.freedesktop.org/show_bug.cgi?id=85052
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If --enable-qmi-username isn't explicitly used, we should just check
for the root user UID, without using getpwnam(). See e.g. these SELinux warnings:
SELinux is preventing /usr/bin/bash from read access on the file /etc/passwd.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that bash should be allowed read access on the passwd file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do allow this access for now by executing:
# grep qmi-proxy /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
|
|
|
|
|
|
| |
Adding a udev rule to change ownership of all QMI devices to the
configured user specified at compile time using --enable-qmi-username
flag.
|
|
|
|
|
| |
This shouldn't be a proxy-only setting. We're going to chown the QMI devices to
this specific user, so we'll re-use this setting for that as well.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently, the QMI proxy process assumes that it is run as root user and
that all incoming client connection users are also root.
However, it's not always preferable to run the QMI proxy as root for
security reasons. On some platforms, the QMI proxy could be constrained
to run as a less-privileged user and specially granted the permission to
access the QMI device. So, adding a compile time flag in libqmi to check
for the specified user, rather than assume it to be the root user. If the flag
is not sent, it'll revert to the existing behaviour of checking for
user=root(i.e UID=0)
|
|
|
|
|
| |
Not an official release, just a version bump to tag the availability of the
new A-GPS related commands.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Don't split requirements per product built, but per actual requirement.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
I don't have it in gnome-ostree, nor at the moment man page stuff in
general.
|
| |
|
| |
|
|
|
|
|
| |
Let it be 0.0.0 for now; we have not updated this in the past versions, but we
should do it from now on.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The pregenerated docs will be in the dist tarball, and will even
be installed with 'make install' when building the dist tarball.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Message traces have been very useful when debugging issues in the protocol, and
we should avoid requiring a full recompilation in order to get them enabled.
Instead, we provide two new API methods, `qmi_utils_(get|set)_traces_enabled()',
which allow specifying whether traces should be dumped with g_debug() or not.
|
|
|
|
|
| |
Also simplify the build by using BUILT_SOURCES to avoid needing to specify
custom dependency rules.
|