[PATCH] libmbim: Add mbim-proxy support
gpsuarez2512 at gmail.com
Tue May 27 09:46:34 PDT 2014
On Mon, May 26, 2014 at 8:04 AM, Aleksander Morgado <
aleksander at aleksander.es> wrote:
> On 05/26/2014 09:36 AM, Bjørn Mork wrote:
> > <quote>
> > 10.5.30 MBIM_CID_DEVICE_SERVICE_SUBSCRIBE_LIST
> > 10.5.30.1 DESCRIPTION
> > The host uses this CID to inform the function of the CIDs for which the
> > host wishes to receive unsolicited events via
> > MBIM_INDICATE_STATUS_MESSAGE. As a result, the function must only
> > indicate notifications for CIDs which have been enabled via this CID.
> > The host updates this list appropriately as its state changes. State
> > changes at the host are possibly triggered by events received from the
> > function (including “wake up” from dormant states). Upon re‐enabling
> > suppressed notifications the host is responsible for synchronizing to
> > the latest device state by performing queries for those CIDs.
> > Upon OPEN_DONE completion, notifications for CIDs defined in this
> > specification are enabled (aka subscribed to) by default, and vendor
> > extension notifications are off by default.
> > </quote>
> > Sorry to completely destroy this interesting discussion :-)
> Ah, look, nice ;) How could I miss that!
> So we should now try to track in the proxy which notifications were
> enabled/disabled by each client via this method, considering all the
> standard ones enabled by default.
Should the tracking be put in MbimDevice instead of the proxy so that
the behavior is the same with or without the proxy? This would prevent
any future "it worked without the proxy but with the proxy we're not
receiving indications" issues.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libmbim-devel