Huawei E1732 qmilib supported?

[Bjørn Mork]

Madhan <madhan.mepco at gmail.com> writes:

> hi bjorn,
> Is it possible create a character device file by using cdc_ncm alone
> (/dev/cdc-ncmx ) ?
> By doing so , we might not require sub driver just to send AT commands , we
> can send AT commands directly
> to the dev file created by cdc-ncm
> am i rite Bjorn ?Is it possible ?

That's basically what Enrico's new driver will do.

I do not think this should be added to the cdc_ncm class driver, simply
because it's pointless for most NCM devices and we don't know of any
supported device using the proper NCM class codes.  A dedicated driver
for this type of device is much better.

The sub-driver part is just an implementation detail.  It makes it
possible to reuse an existing driver to create the character device,
avoiding code duplication and taking advantage of many years of driver
development and testing.  You'll notice that two modules are loaded
instead of one, but we use most of the code from the "extra" module
anyway so the overhead is negligible.

The device naming can be considered confusing, given that we now have 3
different protocols exported as /dev/cdc-wdmX.  But the Huawei variant
doesn't add any new protocol.  AT commands is already the original WDM
class protocol as implemented by e.g Ericsson.




Bjørn





> On Tue, Sep 24, 2013 at 2:53 PM, david preetham <preetham.david at gmail.com>wrote:
>
>> thanks Bjorn,
>> http://patchwork.ozlabs.org/patch/269325/ served my purpose i am using
>> devices E303 (AT cmds for management and NCM protocol for data
>> transfer).The patch you shared registering subdriver cdc-wdm for control
>> endpoint and cdc_ncm driver for bulk endpoints. If i send
>> at^ndisdip=1,1,"apn","","",2 through /dev/cdc-wdmX once i will get response
>> and after that running udhcpc on wwanX interface connecting to network.
>>
>>
>>
>> On Mon, Sep 2, 2013 at 12:57 PM, Bjørn Mork <bjorn at mork.no> wrote:
>>
>>> david preetham <preetham.david at gmail.com> writes:
>>>
>>> > Hi Bjorn Thanks for the reply.
>>> >
>>> > Can i know which are equivalent drivers can load for ndis interface in
>>> > huawei E3121 device?
>>> > The network interface is qmi + ncm based.
>>>
>>> It is?  Haven't heard about that combination before.  Do you have a
>>> "lsusb -v" ouput for that device.  Huawei are nice enough to use the
>>> subclass and protocol fields to separate different function types.  I
>>> wonder what this device says..
>>>
>>> > will cdc_ncm for data plane and cdc_wdm for control interface will work?
>>> > Which driver handling qmi and ncm protocol.
>>>
>>> This is getting a bit ugly.  But Enrico Mioso has created a NCM driver
>>> similar to qmi_wwan, exposing the embedded management channel as a
>>> /dev/cdc-wdmX device: http://patchwork.ozlabs.org/patch/269325/
>>>
>>> The driver was made for modems using AT commands on the management
>>> channel, but it should work equally well with QMI.  I guess it will be
>>> up to ModemManager to guess the protocol based on either probing or
>>> device ID...  The driver won't know.
>>>
>>> But this driver is not yet merged.  It is work in progress.  You'll need
>>> the two other patches in the series if you want to test it now:
>>>
>>> http://patchwork.ozlabs.org/patch/269327/
>>> http://patchwork.ozlabs.org/patch/269326/
>>>
>>>
>>> Bjørn
>>>
>>
>>
>> _______________________________________________
>> libqmi-devel mailing list
>> libqmi-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
>>
>>