Re: Huawei E5786

[Bjørn Mork <bjorn mork no>]

Juha Koskiniemi <juha koskiniemi gmail com> writes:

>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           2
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass      2
>       bInterfaceProtocol     18

Is supported by the option driver:

bjorn@miraculix:/usr/local/src/git/linux$ git grep '0x02, 0x12' drivers/usb/serial/option.c
drivers/usb/serial/option.c:    { USB_VENDOR_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, 0xff, 0x02, 0x12) },

>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        1
>       bAlternateSetting       0
>       bNumEndpoints           1
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass      2
>       bInterfaceProtocol     22

Is supported by the huawei_cdc_ncm driver:

bjorn@miraculix:/usr/local/src/git/linux$ git grep '0x02, 0x16' drivers/net/usb/
drivers/net/usb/huawei_cdc_ncm.c:       { USB_VENDOR_AND_INTERFACE_INFO(0x12d1, 0xff, 0x02, 0x16),

>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        1
>       bAlternateSetting       1
>       bNumEndpoints           3
>       bInterfaceClass       255 Vendor Specific Class
>       bInterfaceSubClass      2
>       bInterfaceProtocol     22
>       iInterface              9 CDC Network Data

Data setting for the NCM function.  Will be activated by the
huawei_cdc_ncm driver driver.

>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        2
>       bAlternateSetting       0
>       bNumEndpoints           2
>       bInterfaceClass         8 Mass Storage
>       bInterfaceSubClass      6 SCSI
>       bInterfaceProtocol     80 Bulk-Only
>       iInterface              4 Mass Storage

And this is of course supported by the usb-storage driver.

So all these functions are supported and has been for a long time. The
drivers will bind automatically. Any any attempt to write to a "new_id"
file will just mess up things.  That is in general a bad idea with any
composite device.  Drivers like "option" will happily bind to most
functions, whether they are serial or not.

The default drivers can of course still fail to bind due to problems we
don't see here (failure to initialize etc), but that should at least end
up as an error in the log.


Bjørn