Modem hotplug behavior inconsistent

[Aleksander Morgado]

Hey,

>
> I'm see something odd that I think may be related to the new device filter
> policy stuff and before digging into it too far I wanted to run it by you
> and see if this sounds like an issue.
>
> When running 'mmcli -m 0 -e' the modem is not flagged as hotplugged
> (enabling_started(), mm-bb-modem.c), however when doing an 'Enable' call "b,
> true" to the dbus ".Modem" interface the modem IS flagged as hotplugged.
> Thus the behavior for the '->enabling_modem_inti' overload is different
> depending on your method of modem enable. I'm happy to trace it down and
> send in the debug once you confirm if this is not desired behavior.
>

That is surprising, as "mmcli -m 0 -e" actually just does a DBus
Enable call passing 'true'. There has to be some other thing happening
somewhere.
The whole "hotplugged" flag is just to get a hint on whether the
device has been just plugged in (i.e. the device appeared while MM was
already running) or otherwise MM found it on startup. There's some
different logic applied in those cases during the enabling phase.


-- 
Aleksander
https://aleksander.es