cdc-wdm: unable to connect after suspend

[Aleksander Morgado]

(left netdev@ out)

On Thu, Jun 12, 2014 at 10:10 PM, Florian Klink <flokli at flokli.de> wrote:
>> Well, I guess we should try to detect the indication and if so, use it
>> as 'reply' to the request we sent. Luckily both the indication and the
>> response will have the same info:
>>
>>     imbim_message_register_state_notification_parse (
>>             notification,
>>             NULL, /* nw_error */
>>             &register_state,
>>             NULL, /* register_mode */
>>             &available_data_classes,
>>             NULL, /* current_cellular_class */
>>             &provider_id,
>>             &provider_name,
>>             NULL, /* roaming_text */
>>             NULL, /* registration_flag */
>>             NULL)
>>
>>         mbim_message_register_state_response_parse (
>>             response,
>>             NULL, /* nw_error */
>>             &register_state,
>>             NULL, /* register_mode */
>>             &available_data_classes,
>>             NULL, /* current_cellular_class */
>>             &provider_id,
>>             &provider_name,
>>             NULL, /* roaming_text */
>>             NULL, /* registration_flag */
>>             NULL)
>>
>> Ugly hack, but I guess there's no other way to handle this firmware issue?
>
>
> I'd think this approach at least seems to be less error-prone than the
> one suggested below. Can you provide me a patch that treats the
> indication as a reply?
> I never touched libmbim, but I'd happily test a patch :-)

The patch should go into ModemManager, but yes, I'll try to write one
for you to test.

-- 
Aleksander
https://aleksander.es