MS basic connect extensions: 0d3a or 9d3a?
benchan at chromium.org
Mon Sep 10 15:36:37 UTC 2018
Looks like the UUID for basic connect extension is pretty messed up. It
isn't listed in http://compliance.usb.org/mbim/. I'm not sure what to
expect. majority wins? Worst case, we will need to carry a quirk in
libmbim to treat them interchangeable, sigh :(
Service UUID = 3d01dcc5-fef5-4d05-9d3a-bef7058e9aaf
Service UUID = 3d01dcc5-fef5-4d05-0d3a-bef7058e9aaf
On Mon, Sep 10, 2018 at 8:22 AM Ben Chan <benchan at chromium.org> wrote:
> Hi Aleksander,
> Looks like Microsoft uses inconsistent UUIDs for the same MS basic
> Service = MBB_UUID_BASIC_CONNECT_EXT_CONSTANT
> Service UUID = 3d01dcc5-fef5-4d05-9d3a-bef7058e9aaf
> UUID = UUID_BASIC_CONNECT_EXTENSIONS
> UUID Value = 3d01dcc5-fef5-4d05-0d3a-bef7058e9aaf
> I added the extensions based on the PCO CID. Given the close
resemblance of these two UUIDs, it looks more like a typo in their doc. I
tested with Fibocom L850, which supports the PCO CID and uses the 9d3a
variant. Unfortunately, I don't have another modem to compare with.
> On Mon, Sep 10, 2018 at 6:59 AM Aleksander Morgado <
aleksander at aleksander.es> wrote:
>> Hey Ben & all,
>> In libmbim we have the MS basic connect extensions UUID defined as:
>> Which is in line with e.g.
>> But then I'm seeing devices reporting the basic connect extensions UUID
>> Which is actually in line with e.g.
>> What is this mess...? Are both UUIDs used interchangeably?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the libmbim-devel