[PATCH c2] huawei: handle disconnection via ^NDISSTAT unsolicited message

Ben Chan benchan at chromium.org
Wed Sep 18 01:51:39 PDT 2013


And can't the modem report the disconnection status right away, and only
> let the bearer afterwards decide whether it wants to disconnect right
> away or defer the disconnection a bit? That would still keep the logic
> within the bearer; and the modem object is just the receiver of the
> unsolicited message which forwards the info to the bearer, which is the
> one applying the logic.
>
>
I'd like to address the deferred disconnection in a follow-up patch. How do
you think about patch v3?


> If we get a NDISSTAT saying we're disconnected by the network and we
> cannot act right away, maybe we can NDISTATQRY? ourselves for some time
> to see when we really got disconnected? Or are the responses of these
> NDISSTATQRY? queries also unreliable? Or maybe we could set the bearer
> in 'disconnecting' state until we make sure that the bearer is fully
> disconnected after some seconds?
>

Probably. I need to run some tests to see if NDISTATQRY? can be used to
confirm ^NDISSTAT.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/modemmanager-devel/attachments/20130918/06689b46/attachment-0001.html>


More information about the ModemManager-devel mailing list