I am trying to understand when/how NCM-NDIS actually broke.
The switch from 374 to 376 branch seems to be the point in time, as @plun already found out: https://www.snbforums.com/threads/3-0-0-4-374-5656-fixes-3g-dongles-huawei.17001/post-129044
By comparing the source code of the two branches, I have found the following new piece of code in /release/src-rt-6.x.4708/linux/linux-2.6.36/drivers/net/usb/cdc_ncm.c which I suspect could be at fault:
This piece of code is still there nowadays in merlin-master: https://github.com/RMerl/asuswrt-me....36/drivers/net/usb/cdc_ncm.c#L1269C1-L1275C4
My belief seems to be confirmed by this report too: https://forums.linuxmint.com/viewtopic.php?t=148990
Any thought about this?
The switch from 374 to 376 branch seems to be the point in time, as @plun already found out: https://www.snbforums.com/threads/3-0-0-4-374-5656-fixes-3g-dongles-huawei.17001/post-129044
By comparing the source code of the two branches, I have found the following new piece of code in /release/src-rt-6.x.4708/linux/linux-2.6.36/drivers/net/usb/cdc_ncm.c which I suspect could be at fault:
Code:
/* tag Huawei devices as wwan */
{ USB_VENDOR_AND_INTERFACE_INFO(0x12d1,
USB_CLASS_COMM,
USB_CDC_SUBCLASS_NCM,
USB_CDC_PROTO_NONE),
.driver_info = (unsigned long)&wwan_info,
},This piece of code is still there nowadays in merlin-master: https://github.com/RMerl/asuswrt-me....36/drivers/net/usb/cdc_ncm.c#L1269C1-L1275C4
My belief seems to be confirmed by this report too: https://forums.linuxmint.com/viewtopic.php?t=148990
Any thought about this?
