diff options
author | Dan Williams <dcbw@redhat.com> | 2016-06-17 10:39:02 -0500 |
---|---|---|
committer | Dan Williams <dcbw@redhat.com> | 2016-07-11 11:02:53 -0500 |
commit | 48f02107395986c31b95067b5f08de256dab3c18 (patch) | |
tree | 71874819336ef757b270b2a3c07f896fdc5886f0 /examples/modem-watcher-javascript/main.js | |
parent | d757c32b945da7eafcd95080b30116c98f4e665d (diff) |
bearer-mbim: use the context IP type MM asked to be activated instead of modem response
MM never passes MBIM_CONTEXT_IP_TYPE_DEFAULT which would require paying
attention to the ip_type in the reply to figure out what type the modem
activated. Instead, MM always specifies the ip_type it wants to activate,
and some modems (K5160) return a different type in the response. The modem
is required to activate the type MM asks for or return an error, so if
the activation was successful we can safely assume the modem activated
the ip_type we want, and we can ignore the ip_type in the response.
Diffstat (limited to 'examples/modem-watcher-javascript/main.js')
0 files changed, 0 insertions, 0 deletions