Hi Aleksander,
thanks for the review!
Here's the parsing patch, the plugin will follow later.
diff --git a/src/mm-modem-helpers.c b/src/mm-modem-helpers.c
index 17ad8d2..a9b1c71 100644
--- a/src/mm-modem-helpers.c
+++ b/src/mm-modem-helpers.c
@@ -131,6 +131,58 @@ mm_split_string_groups (const
Aleksander Morgado writes:
> I've compared both logs and they really are mostly similar.
Yes. Thanks for confirming that. It's so easy to miss something..
> The only notable difference between the two is an extra "NAS Get
> Serving System" happening in the middle
This patch series adds supported and current modes loading for Telit plugin
Daniele Palmas (2):
plugin: telit: add supported modes loading
plugin: telit: add current mode loading
plugins/telit/mm-broadband-modem-telit.c | 186 +++
1 file changed, 186
This patch add supported modes loading in Telit plugin.
---
plugins/telit/mm-broadband-modem-telit.c | 104 +++
1 file changed, 104 insertions(+)
diff --git a/plugins/telit/mm-broadband-modem-telit.c
b/plugins/telit/mm-broadband-modem-telit.c
index 77b1800..5b3d18c
Aleksander Morgado writes:
>> I did some more experimenting and found that an "USB reset" somehow
>> resolves this problem as well. It will reset the USB bus connection,
>> causing drivers to unbind and rebind and therefore a full new modem
>> discovery by MM. But it
On Mon, Feb 1, 2016 at 7:53 AM, Dan Williams wrote:
>> http://cgit.freedesktop.org/ModemManager/ModemManager/commit/?id=aeb6
>> 3621723fd3d7e39870466d2cffcf56fc6570
>
> One downside I note is that with g_task_propagate_pointer() we no
> longer have easy access to pointer itself,
On Sat, 2016-01-30 at 19:27 -0800, Aleksander Morgado wrote:
> Hey hey,
>
> ModemManager git master is already using GTask already for some
> things, instead of the good old GSimpleAsyncResult. GTask was
> released
> in GLib/GIO 2.36, and it has a really good API, including built-in
>
Hey,
>
>> I've compared both logs and they really are mostly similar.
>
> Yes. Thanks for confirming that. It's so easy to miss something..
>
>> The only notable difference between the two is an extra "NAS Get
>> Serving System" happening in the middle between the WDS client CID
>> allocation