Carrier certification with libqmi ?

[Ramesh Siripurapu]

>>>
>>>  SLQSOMADMStartSession ( ULONG sessionType )
>>
>>  I believe this comes from the Sierra Wireless QMI SDK? And it is
>>  probably specific to Sierra Wireless QMI devices. I haven't looked at
>>  how it is implemented, but I assume it depends on SWI firmware features.
>>  That would of course not prevent it from being implemented in libqmi
>>  (like the SWI FCC thingy). But you should be aware that it won't
>>  necessarily be valid for any generic Gobi device.
>
> Curious as I am, I had to look at this. Unless I'm reading something
> wrong, then this function use an 0x4e20 message id in the 0xf0 QMI
> service - for which we have no docs AFAIK. The high service number
> might indicate a vendor specific range? But we'd need to know a lot
> more to be able to reimplement this feature. For now you're probably
> better off using the vendor supported SDK for stuff like this.
>

Yes. That is from Sierra Wireless QMI SDK. What does it take to add this CI FUMO support to qmi ? Is it reverse engineering messages sent and received by QMI SDK using usbmon and defining qmi-service-swioma.json in libqmi accordingly ?