Re: [PATCH] broadband-modem-mbim: parse nw_error in register_state_set_ready only if MBIM_STATUS_FAILURE

Hi Aleksander, Thank you for such a swift response! I will post updated patch shortly, after testing updated changes locally. W dniu 21.03.2019 o 13:42, Aleksander Morgado pisze: > Hey! > > See comments below. > > On Thu, Mar 21, 2019 at 1:14 PM Lech Perczak > wrote: >

[PATCH v2] broadband-modem-mbim: parse nw_error in register_state_set_ready only if MBIM_STATUS_FAILURE

unconditionally if MBIM status code is MBIM_STATUS_FAILURE. Therefore, check NwError IFF MBIM response status code equals MBIM_STATUS_FAILURE, instead of MBIM_STATUS_SUCCESS. Fixes: 854c371c8aa9 ("broadband-modem-mbim: implement 3GPP registration request") Signed-off-by: Lech Perczak -

Re: [PATCH] broadband-modem-mbim: parse nw_error in register_state_set_ready only if MBIM_STATUS_FAILURE

Hi Aleksander, Any update on the patch? :) In the meantime I got response from Telit that they won't fix the original problem which made me create this patch. With kind regards, Lech W dniu 21.03.2019 o 13:14, Lech Perczak pisze: > Some modems (Namely: Telit LE910 V2) report nonzero

Re: cannot find glib-2.0 when building in openwrt

>> >> Ideas? I'm on actual 18.06 branch. Thanks. >> >> BR, >> >> marek >> >> --  >> as simple and primitive as possible >> - >> Marek Belisko - OPEN-NANDRA >&

Timing of next major release

ch instead? -- Pozdrawiam/With kind regards, Lech Perczak Sr. Software Engineer Camlin Technologies Poland Limited Sp. z o.o. ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel

Segfault in MM 1.12.4 in port timeout detection logic

= 0x0, mbim = 0x0} I have a full session log and a core dump, so pretty much anything could be extracted if needed. So far it only reproduced once. I'm also analyzing myself how to fix it, but I'd be glad if you could take a look at this. -- Pozdrawiam/With kind regards, Lech Perc

Re: Segfault in MM 1.12.4 in port timeout detection logic

than the >> modem object, and so by the time the timed-out signal is emitted, the >> modem object is already unrefed. The fix for this issue is to keep >> track of all signal ids returned by g_signal_connect(port, >> "timed-out",...) and make sure they ar

Re: Segfault in MM 1.12.4 in port timeout detection logic

;m also analyzing >>> myself how to fix it, but I'd be glad if you could take a look at this. >>> >> The error makes sense; the port object is living for longer than the >> modem object, and so by the time the timed-out signal is emitted, the >> modem ob

Issues regarding multiple MBIM bearer support

8 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/networking/cdc_mbim.rst?id=92f06f4226fd9bdd6fbbd2e8b84601fc14b5855e#n173 [3] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/05b005951710c8810538ec448e89e32f28c3d592 -- Pozdrawiam/With kind regards, L

Re: Issues regarding multiple MBIM bearer support

tlab for > analysis. > > > > ModemManager only recently gained full support for PDN multiplexing. For > > full support of this, ModemManager most probably should pass the > > information about used PDN session index to NetworkManager, > > which would then setup the VLA

Re: ModemManager update

Hey Artur, Aleksander, I think your best bet is compiling .deb's based on source files available from Sid: https://packages.debian.org/sid/libqmi-glib5 https://packages.debian.org/sid/libmbim-glib4 https://packages.debian.org/sid/modemmanager These are IIRC the latest release, or very close to

[PATCH] broadband-modem-mbim: parse nw_error in register_state_set_ready only if MBIM_STATUS_FAILURE

ronize ModemManager's internal state, preventing connection until MM or modem restart. Fixes: 854c371c8aa9 ("broadband-modem-mbim: implement 3GPP registration request") Signed-off-by: Lech Perczak --- src/mm-broadband-modem-mbim.c | 31 --- 1 file changed,

Random QMI port probe failures after ed13e053cd42 ("port-probe: fix custom init probing not having open AT port")

\0W\0\12\1\0\4\0\15\1\0\0\0\16\2\0\0\0\17\1\0\0\0\18\1\0\0\0\20\1\0\0\0\23\1\0\0\0\24\1\0\0\0\26\1\0\16\0\29\1\0\1\0\31\1\0\0\0!\1\0\0\0"\1\0\0\0$\1\0\0\0)\1\0\0\0*\1\0\0\00\1\0\0\02\1\0\0\06\1\0\0\0I\1\0\0\0\231\1\0\0\0\232\1\0\0\0\235\1\0\0\0\237\1\0\0\0' ModemManager[13321]:   [1734

Re: Random QMI port probe failures after ed13e053cd42 ("port-probe: fix custom init probing not having open AT port")

__ > > This email originated from outside of Camlin Group. Do not click on links or > open attachments unless you are confident they are secure. If in doubt, > please raise a security incident via the following portal: Camlin Helpdesk – > Report an Information Security Incident/Non-C