f1712c606c
NCM specs are not actually mandating a specific position in the frame for the NDP (Network Datagram Pointer). However, some Huawei devices will ignore our aggregates if it is not placed after the datagrams it points to. Add support for doing just this, in a per-device configurable way. While at it, update NCM subdrivers, disabling this functionality in all of them, except in huawei_cdc_ncm where it is enabled instead. We aren't making any distinction between different Huawei NCM devices, based on what the vendor driver does. Standard NCM devices are left unaffected: if they are compliant, they should be always usable, still stay on the safe side. This change has been tested and working with a Huawei E3131 device (which works regardless of NDP position) and an E3372 device (which mandates NDP to be after indexed datagrams). Signed-off-by: Enrico Mioso <mrkiko.rs@gmail.com> Signed-off-by: Matti Laakso <malaakso@elisanet.fi> SVN-Revision: 46464 |
||
|---|---|---|
| .. | ||
| adm5120 | ||
| adm8668 | ||
| ar7 | ||
| ar71xx | ||
| arm64 | ||
| at91 | ||
| ath25 | ||
| au1000 | ||
| bcm53xx | ||
| brcm47xx | ||
| brcm63xx | ||
| brcm2708 | ||
| cns3xxx | ||
| gemini | ||
| generic | ||
| imx6 | ||
| ipq806x | ||
| ixp4xx | ||
| kirkwood | ||
| lantiq | ||
| malta | ||
| mcs814x | ||
| mpc85xx | ||
| mvebu | ||
| mxs | ||
| netlogic | ||
| octeon | ||
| omap | ||
| omap24xx | ||
| orion | ||
| oxnas | ||
| ppc40x | ||
| ppc44x | ||
| pxa | ||
| ramips | ||
| rb532 | ||
| realview | ||
| sunxi | ||
| uml | ||
| x86 | ||
| xburst | ||
| Makefile | ||