summaryrefslogtreecommitdiff
path: root/src/mbim-proxy
Commit message (Collapse)AuthorAgeFilesLines
* mbim-proxy: update copyrightAleksander Morgado2023-04-141-2/+2
|
* mbimcli,mbim-proxy: add missing initializers in GOptionEntry arrayAleksander Morgado2022-12-011-1/+1
| | | | | | | | | To avoid compiler warnings like: [96/113] Compiling C object src/mbimcli/mbimcli.p/mbimcli-ms-basic-connect-extensions.c.o ../src/mbimcli/mbimcli-ms-basic-connect-extensions.c:133:11: warning: missing field 'short_name' initializer [-Wmissing-field-initializers] {NULL } ^ 1 warning generated.
* mbim-proxy: add --verbose-full flagChristof Meerwald2022-11-021-2/+15
|
* mbim-proxy: compute log time string only if printing the logAleksander Morgado2022-08-051-13/+12
|
* build: Fix double quotes in rules fileIñigo Martínez2021-10-261-1/+1
| | | | | | | | | | | | | | `MBIM_USERNAME` is quoted twice in the `76-mbim-proxy-device-ownership.rules` rules file. This is because the definition is used in two files. The first one is `config.h` file, that is used in source code files and needs to be explicitly quoted. The second one is the rules file, mentioned above that already has quotes in the template file. The explicit quotes have been removed in the rules file generation. Fixes #21
* build: Use / instead of join_pathsIñigo Martínez2021-09-131-1/+1
| | | | | | | 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-
* mbim-proxy: replace license boilerplate by SPDX identifiersYegor Yefremov2021-07-292-13/+3
|
* build: Remove autotoolsIñigo Martínez2021-07-271-31/+0
| | | | | | | To avoid the burden of maintaining multiple build systems, autotools support has been removed. Fixes #18.
* meson: fix SPDX license identifierYegor Yefremov2021-07-251-1/+1
| | | | | | 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.
* build: port to meson build systemIñigo Martínez2021-05-031-0/+22
| | | | | | 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.
* core: update copyright years to 2021Aleksander Morgado2021-01-171-1/+1
|
* mbim-proxy: port to use g_auto() helpersAleksander Morgado2020-05-111-5/+3
|
* mbim-proxy: flag print_version_and_exit() as noreturnEric Caruso2020-02-061-0/+1
|
* build: bump copyright years to 2020Aleksander Morgado2020-01-031-1/+1
|
* mbim-proxy: fix warnings with -Wswitch-enumAleksander Morgado2019-11-201-1/+7
| | | | | | | | | | mbim-proxy.c: In function ‘log_handler’: mbim-proxy.c:101:5: warning: enumeration value ‘G_LOG_FLAG_RECURSION’ not handled in switch [-Wswitch-enum] 101 | switch (log_level) { | ^~~~~~ mbim-proxy.c:101:5: warning: enumeration value ‘G_LOG_LEVEL_MESSAGE’ not handled in switch [-Wswitch-enum] mbim-proxy.c:101:5: warning: enumeration value ‘G_LOG_LEVEL_INFO’ not handled in switch [-Wswitch-enum] mbim-proxy.c:101:5: warning: enumeration value ‘G_LOG_LEVEL_MASK’ not handled in switch [-Wswitch-enum]
* build: use AX_IS_RELEASE() and AX_COMPILER_FLAGS()Aleksander Morgado2019-11-201-0/+2
| | | | | | | | | | | | | | The autoconf macros AX_COMPILER_FLAGS_{CFLAGS|GIR|LDFLAGS} test for compiler and linker support of various flags, and add the flags to the generated output. If the command-line option '--enable-compile-warnings' is specified to 'configure', a number of additional warning options is also added to the output. This is the default. This update requires the presence of the GNU autoconf-archive in the system when building from git (not required when building from a source tarball).
* build: rework cflags/cppflags/ldflagsAleksander Morgado2019-11-191-4/+8
|
* mbim-proxy: new '--empty-timeout=[SECS}' optionaleksander/mbim-proxy-timingAleksander Morgado2019-03-071-5/+18
| | | | | We allow specifying how long the proxy should be kept running after the last client/device has exited.
* mbim-proxy: new --no-exit option to avoid the proxy from exitingAleksander Morgado2019-03-071-9/+17
|
* mbim-proxy: update default empty lifetime timeout to 300sAleksander Morgado2019-03-071-1/+1
|
* build: bump copyrights to 2019Aleksander Morgado2019-01-081-1/+1
|
* mbimcli,mbim-proxy,mbim-network: update copyright year to 2018Aleksander Morgado2018-01-201-2/+2
|
* glib: remove invocations of g_type_init()Ben Chan2017-06-271-4/+0
| | | | | | | g_type_init() has been deprecated (and also marked with the attribute 'deprecated') since glib 2.36 as the type system is automatically initialized. Since the minimum version of glib required by libmbim is 2.36, calling g_type_init() isn't necessarily in the libmbim code.
* glib: guard invocations of g_type_init()Ben Chan2017-02-031-0/+2
| | | | | | | | | | g_type_init() has been deprecated (and also marked with the attribute 'deprecated') since glib 2.36 as the type system is automatically initialized. Since the minimum version of glib required by libmbim is 2.32, calling g_type_init() should be guarded with the GLIB_CHECK_VERSION macro. When libmbim later requires at least glib 2.36, we can completely remove all invocations of g_type_init() from the code.
* libmbim-glib,utils: avoid getpwnam() call if --enable-mbim-username not usedAleksander Morgado2015-01-091-1/+1
| | | | | | | | | | | | | | | | If --enable-mbim-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 mbim-proxy /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp
* libmbim-glib,proxy: Correct the driver name in the MBIM proxy UDEV rule.Roshan Pius2014-12-221-1/+1
| | | | | Fixing a bug in the previous commit to add udev rules for MBIM proxy devices.
* libmbim-glib,proxy: Change ownership of MBIM devices to the configured user.Roshan Pius2014-12-222-0/+21
| | | | | | Adding a udev rule to change ownership of all MBIM devices to the configured user specified at compile time using --enable-mbim-username flag.
* mbim-proxy: wait up to 30s if last device is goneAleksander Morgado2014-07-311-2/+11
| | | | | | A device being 'gone' doesn't only mean that it was disconnected and we can no longer talk to it; it may also be that the proxy couldn't perform the full open sequence and therefore it removes it from its records.
* mbim-proxy: Exit when all devices are removedGreg Suarez2014-07-311-0/+20
| | | | | | Exit when all devices are removed instead of when there are no clients connected. This is done to allow for --no-close and --no-open options in mbimcli.
* libmbim-glib: changed copyright from Greg Suarez to Smith Micro Software, Inc.Greg Suarez2014-07-311-1/+1
|
* libmbim: Add mbim-proxy supportGreg Suarez2014-07-312-0/+239
This patch implements the mbim-proxy support to allow mulitple clients to have concurrent access to the MBIM device through libmbim. The implementation is heavily based on qmi-proxy. The function mbim_device_open_full() is provided for clients to specify that the device should be opened through the mbim-proxy via the flag MBIM_DEVICE_OPEN_FLAGS_PROXY. The function mbim_device_open() will behave as it has before and open the device directly. Proxy Control: A new service UUID is created to allow for clients to control the proxy. This service is currently only used to pass on the device path (/dev/cdc-wdm*) the client is requesting to open. In the future CIDs will be added to allow for setting the MaxControlMessage size and setting timeout for specific messages. Unknown UUIDs: Currently the mbim-proxy will allow messages with unknown UUIDs to pass through. The proxy will track unknown UUIDs sent by the client and device notifications matching the tracked UUID will be sent to the client. Device notifications of known UUIDs will be sent to all connected clients. Signed-off-by: Greg Suarez <gsuarez@smithmicro.com>