Hey,
>
> sorry for the long -email, but I got stuck again in another problem: the
> re-probe does not start when the ModemManager is in "SIM missing failed
> state" and mm_base_modem_set_valid(..., false) is called.
>
> The current, modified, initialization code has got the following new steps:
>
>
Hi all,
sorry for the long -email, but I got stuck again in another problem: the
re-probe does not start when the ModemManager is in "SIM missing failed
state" and mm_base_modem_set_valid(..., false) is called.
The current, modified, initialization code has got the following new steps:
1. mm-ifa
Hi Aleksander,
thank you for this reply, lot of information and clear.
Carlo
On 23 March 2016 at 10:06, Aleksander Morgado
wrote:
> Hey!
>
> On Tue, Mar 22, 2016 at 3:25 PM, Carlo Lobrano
> wrote:
> > I had some time now to look at the changes for SIM hot insertion feature
> > (QSS unsolicite
Hey!
On Tue, Mar 22, 2016 at 3:25 PM, Carlo Lobrano wrote:
> I had some time now to look at the changes for SIM hot insertion feature
> (QSS unsolicited in Telit modems), lot of doubts actually.
>
> My idea is the following:
>
> 1. in modem iface initialization, ask the modem whether it supports
Hi Aleksander,
I had some time now to look at the changes for SIM hot insertion feature
(QSS unsolicited in Telit modems), lot of doubts actually.
My idea is the following:
1. in modem iface initialization, ask the modem whether it supports or not
SIM hot insertion (TBD: sync method? property?).
Thanks a lot! I'll have a look at that
Carlo
Il dom 13 mar 2016 11:57 AM Aleksander Morgado
ha scritto:
> On Sun, Mar 13, 2016 at 10:25 AM, Carlo Lobrano
> wrote:
> > That looks like a lot of work :D, better design all the changes before
> > starting.
>
> Well, maybe not much work, but probabl
On Sun, Mar 13, 2016 at 10:25 AM, Carlo Lobrano wrote:
> That looks like a lot of work :D, better design all the changes before
> starting.
Well, maybe not much work, but probably a bit hard to get the logic right.
> Brief recap
> 1. Put the modem in failed state
You may want to check what happ
That looks like a lot of work :D, better design all the changes before
starting.
Brief recap
1. Put the modem in failed state
2. Keep a port open when in failed state but with handlers still assigned
to unsolicited
3. start a full reprobe
Another problem I saw is that when the SIM is not inserted
On Fri, Mar 11, 2016 at 5:21 PM, Carlo Lobrano wrote:
> I'm trying to update some modem data according to an unsolicited event.
>
> Telit modems have an unsolicited indication #QSS (Query SIM Status) which is
> emitted when the SIM status changes (e.g. SIM removed/inserted).
>
> My intention is to
Hi all,
I'm trying to update some modem data according to an unsolicited event.
Telit modems have an unsolicited indication #QSS (Query SIM Status) which
is emitted when the SIM status changes (e.g. SIM removed/inserted).
My intention is to register an handler to this notification and somehow
tr
10 matches
Mail list logo
