ZTE MF823 autoswitch

[Markus Gothe]

Actually ZTE piggyback on f_mbim.c from Qualcomm and can be found here: ‎https://android.googlesource.com/kernel/msm/+/android-msm-3.9-usb-and-mmc-hacks/drivers/usb/gadget/f_mbim.c

There we can study the behaviour of the ctrl request etc.

Sent from my BlackBerry 10 smartphone.
  Original Message  
From: Bjørn Mork
Sent: måndagen den 12:e september 2016 14:11
To: Markus Gothe
Cc: libmbim List; Gareth Lowe
Subject: Re: ZTE MF823 autoswitch

Markus Gothe <nietzsche at lysator.liu.se> writes:

> So this is how ZTE implements Microsofts "identity mophing" as
> described here:
> https://msdn.microsoft.com/windows/hardware/drivers/network/mb-identity-morphing
>
> The software waits for the OS to send an MS properitary "OS
> descriptor‎" to detect if the OS supports MBIM or not.

OK, so that should be pretty easy to implement in userspace, using libusb.
Maybe something for usb_modeswitch?

Did you try it out? From memory, the Microsoft protocol is pretty
simple:

1) request string descriptor 0xee - this returns "MSFT100<X>"
2) use the <X> magic code as vendor control device/interface request,
where wIndex specifies the wanted feature page

I assume the detection stops there? The point of the Microsoft MBIM
requirements were to prevent mode switching. Or does the ZTE feature
table specify a "hidden" USB configuration number for MBIM? Do you have
an example of what the ZTE feature descriptor tables look like?


Bjørn
_______________________________________________
libmbim-devel mailing list
libmbim-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libmbim-devel