Huawei e3272s

[Markus Gothe]

Here is the code for distinguish between QMI and Balong:

         //Begin:DTS2013061403406 added by l81005329 20130614
     if ((HW_JUNGO_BCDDEVICE_VALUE != dev->udev->descriptor.bcdDevice
     && BINTERFACESUBCLASS != intf->cur_altsetting->desc.bInterfaceSubClass
         && BINTERFACESUBCLASS_HW != intf->cur_altsetting->desc.bInterfaceSubClass)
         || ((NULL != info->u)&&(info->u->bMasterInterface0 != info->u->bSlaveInter
face0))) {
             printk(KERN_ERR"lxz device is Qualcomm device bcdDevice=%x,InterfaceSu
bClass=%x\n",
                        dev->udev->descriptor.bcdDevice,intf->cur_altsetting->desc.
bInterfaceSubClass);
             deviceisBalong = false;
         }else{
             deviceisBalong = true;
                 printk(KERN_ERR"lxz device is Balong device bcdDevice=%x,InterfaceSubClass=%x\n",
                        dev->udev->descriptor.bcdDevice,intf->cur_altsetting->desc.bInterfaceSubClass);
         }
         //End:DTS2013061403406 added by l81005329 20130614


//M

On 14 Jul 2015, at 20:55 , Dan Williams <dcbw at redhat.com> wrote:

> On Tue, 2015-07-14 at 19:15 +0200, Markus Gothe wrote:
>> Actually Dan means HiSilicon Balong, since HiLink is the webui feature from Huawei.
> 
> Yeah, I did mean HiSilicon.
> 
> dan
> 
>> Franko had a way to distinguish between QMI-based and Balong-based chipsets... I will check if I can find that code.
>> 
>> //MDen 14 jul 2015 6:10 em skrev Dan Williams <dcbw at redhat.com>:
>>> 
>>> On Tue, 2015-07-14 at 11:09 +0300, Alexey Popov wrote:
>>>> Hi!
>>>> Is there a list of qmi-enabled modems? I have Huawei e3272s usb modem
>>> 
>>> No, there's no list anywhere except the USB IDs in the kernel drivers.
>>> Those are pretty hard to match up to modem model #s though, and
>>> manufacturers use the same USB IDs for completely different hardware.
>>> 
>>>> (probably it has Chipset Qualcomm MSM6290). Does it have qmi capability?
>>> 
>>> Hard to tell, unless you have access to the Huawei Windows drivers to
>>> inspect them.  I looked at some drivers/firmware for the E3272s and it
>>> appears that it's actually not Qualcomm-based, but a HiLink Balong V7R1
>>> chipset.  So it won't support QMI and I think all you can use are AT
>>> commands and the ethernet port.  There should be ModemManager support
>>> for that (via ^NDISDUP) at least.
>>> 
>>>> Should I turn some ports on (with at^setport) in order to get /dev/cdc-wdm
>>>> device?
>>> 
>>> Given that it's likely a HiLink chipset, I don't think that would do
>>> anything useful here.
>>> 
>>> Dan
>>> 
>>> _______________________________________________
>>> libqmi-devel mailing list
>>> libqmi-devel at lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>> _______________________________________________
>> libqmi-devel mailing list
>> libqmi-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
> 
> 
> _______________________________________________
> libqmi-devel mailing list
> libqmi-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel

//Markus - The panama-hat hacker

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 186 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20150714/1c3f7a04/attachment.sig>