QMI via MBIM for "FCC Authentication" fix
Reinhard Speyerer
rspmn at arcor.de
Mon Apr 4 18:57:00 UTC 2016
On Sun, Apr 03, 2016 at 08:06:20PM +0200, Bjørn Mork wrote:
> Emil Ljungdahl <emil at kratern.se> writes:
>
> > The only part in Collins patch that doesn't seem
> > "generic" (for my untrained libmbim eye) is the UUID for QMI that he
> > assumed to be Sierra specific. Any new insights about that or additional
> > UUIDs?
>
> I don't think it is Sierra specific. It is Qualcomm specific, like QMI
> itself. The UUID was mentioned on the Qualcomm Gobi developer forums
> before they were closed for the public.
>
> But I don't have any non-Sierra device based on Qualcomm MBIM code to
> prove it. Anyone else?
Hi Bjørn,
at least a SIMCom SIM7230E also provides this service after switching it
to MBIM mode using echo 2 > .../bConfigurationValue:
# mbimcli -d /dev/cdc-wdm0 --query-device-services | egrep '(Service|UUID):'
Service: 'basic-connect'
UUID: [a289cc33-bcbb-8b4f-b6b0-133ec2aae6df]:
Service: 'sms'
UUID: [533fbeeb-14fe-4467-9f90-33a223e56c3f]:
Service: 'ussd'
UUID: [e550a0c8-5e82-479e-82f7-10abf4c3351f]:
Service: 'phonebook'
UUID: [4bf38476-1e6a-41db-b1d8-bed289c25bdb]:
Service: 'stk'
UUID: [d8f20131-fcb5-4e17-8602-d6ed3816164c]:
Service: 'auth'
UUID: [1d2b5ff7-0aa1-48b2-aa52-50f15767174e]:
Service: 'unknown'
UUID: [d1a30bc2-f97a-6e43-bf65-c7e24fb0f0d3]:
Service: 'ms-host-shutdown'
UUID: [883b7c26-985f-43fa-9804-27d7fb80959c]:
Service: 'unknown'
UUID: [2d0c12c9-0e6a-495a-915c-8d174fe5d63c]:
Service: 'ms-firmware-id'
UUID: [e9f7dea2-feaf-4009-93ce-90a3694103b6]:
Service: 'unknown'
UUID: [5967bdcc-7fd2-49a2-9f5c-b2e70e527db3]:
Service: 'unknown'
UUID: [6427015f-579d-48f5-8c54-f43ed1e76f83]:
Tunneling of QMI_CTL_MESSAGE_GET_VERSION_INFO and
QMI_CTL_GET_CLIENT_ID for the DMS service over MBIM worked for me when
using your swi_setusbcomp.pl script.
Regards,
Reinhard
More information about the libmbim-devel
mailing list