Bug 95302 - [PATCH] mbm: wait until the E2NAP response for disconnecting
Summary: [PATCH] mbm: wait until the E2NAP response for disconnecting
Status: RESOLVED FIXED
Alias: None
Product: ModemManager
Classification: Unclassified
Component: general (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: ModemManager bug user
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-06 17:32 UTC by Lubomir Rintel
Modified: 2016-05-27 17:44 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Patch 1/2 (6.24 KB, text/plain)
2016-05-06 17:32 UTC, Lubomir Rintel 		Details
Patch 2/2 (5.83 KB, text/plain)
2016-05-06 17:32 UTC, Lubomir Rintel 		Details
Show Obsolete (2) View All

Description Lubomir Rintel 2016-05-06 17:32:07 UTC 
Created attachment 123522 [details]
Patch 1/2

Otherwise the client may start connecting again (such as NetworkManager
on autoconnect retry) and the anychronous E2NAP may abort it.
Comment 1 Lubomir Rintel 2016-05-06 17:32:58 UTC 
Created attachment 123525 [details]
Patch 2/2
Comment 2 Dan Williams 2016-05-10 21:21:26 UTC 
Patches look mostly good, except for really old F3507g device firmware.  Those didn't support E2NAP indications, and that's why the polling was implemented.  We should probably also poll for disconnect too.
Comment 3 Dan Williams 2016-05-11 18:21:30 UTC 
I implemented disconnect polling and waiting for the E2NAP response in the dcbw/mbm-connect-disconnect-cleanup branch.  Could you review?
Comment 4 Dan Williams 2016-05-27 17:44:09 UTC 
Merged branch after review from Aleksander.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.