openwrt/upstream - upstream openwrt

	Commit message (Collapse)	Author	Age	Files	Lines
*	kernel: update kernel 3.18 to version 3.18.43	Stijn Tintel	2016-10-24	1	-8/+8
\| \| \| \| \| \| \| \| \| \|	Refresh patches for all targets supporting 3.18 and not marked broken. Compile-tested on all targets using 3.18 and not marked broken. Changes to generic/610-netfilter_match_bypass_default_checks.patch based on 84d489f64f3b382d5544e342f66d8806e94e85d3. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be>
*	kernel: cdc_ncm: Add support for moving NDP to end of NCM frame	Hauke Mehrtens	2015-07-25	1	-48/+81
\| \| \| \| \| \| \| \| \| \| \| \|	This patch was missing for kernel 4.0 and 4.1 in r46464. I also replaced the version in OpenWrt with the version which went upstream into the Linux mainline kernel. This closes #20193 and #20192 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> SVN-Revision: 46493
*	generic: cdc_ncm: Add support for moving NDP to end of NCM frame	John Crispin	2015-07-24	1	-0/+195
	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