Making disconnection more robust
Tim Small
tim at seoss.co.uk
Fri Aug 11 13:58:12 UTC 2017
On 11/08/17 14:09, Aleksander Morgado wrote:
> I'd suggest we try to move
> that modem to "Failed" state instead, as we really lost the control
> port; and let the applications using MM do whatever they need to do
> with a failed modem, including external power cycle or whatever.
Hi,
Yes that makes more sense. That had crossed my mind previously, but I
didn't look into it further.
Presumably it'd be possible to create a separate service which looks for
a particular modem failing, and takes the necessary action to reset and
trigger a reprobe etc.? Would there be any issue with this running at
the same time as nm for instance?
Thanks,
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
More information about the ModemManager-devel
mailing list