mtk-20170518/target, branch v17.01.6 MTK 20170518 : Mediatek SDK based on OpenWRT Barrier Breaker kernel: bump kernel 4.4 to version 4.4.153 2018-08-30T11:07:40+00:00 Hauke Mehrtens hauke@hauke-m.de 2018-08-30T10:47:44+00:00 f712db9df6320b296849378030a66372255ffca2 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> 
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
kernel: bump kernel 4.4 to version 4.4.150 2018-08-21T21:22:57+00:00 Hauke Mehrtens hauke@hauke-m.de 2018-08-21T21:22:01+00:00 9c0bab0059f7caca87a6513b1723d8036300cdf4 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> 
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
kernel: bump kernel 4.4 to version 4.4.148 2018-08-15T17:18:47+00:00 Hauke Mehrtens hauke@hauke-m.de 2018-08-15T16:53:23+00:00 f3865bd4efa8c0fbf82899d0c3072a192f3beaea The following patch was integrated upstream: * target/linux/generic/patches-4.4/005-ext4-fix-check-to-prevent-initializing-reserved-inod.patch This fixes tries to work around the following security problems: * CVE-2018-3620 L1 Terminal Fault OS, SMM related aspects * CVE-2018-3646 L1 Terminal Fault Virtualization related aspects Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de> 
The following patch was integrated upstream:
 * target/linux/generic/patches-4.4/005-ext4-fix-check-to-prevent-initializing-reserved-inod.patch

This fixes tries to work around the following security problems:
 * CVE-2018-3620 L1 Terminal Fault OS, SMM related aspects
 * CVE-2018-3646 L1 Terminal Fault Virtualization related aspects

Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
brcm47xx: revert upstream commit breaking BCM4718A1 2018-08-10T08:37:37+00:00 Rafał Miłecki rafal@milecki.pl 2018-07-27T13:57:13+00:00 583fd4b229b0b85c935ee3ac8b3432c9ef9120c9 This fixes kernel hang when booting on BCM4718A1 (& probably BCM4717A1). Signed-off-by: Rafał Miłecki <rafal@milecki.pl> (cherry picked from commit 4c1aa64b4d804e77dfaa8d53e5ef699fcced4b18) Fixes: aaecfecdcde5 ("kernel: bump kernel 4.4 to version 4.4.139") 
This fixes kernel hang when booting on BCM4718A1 (& probably BCM4717A1).

Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
(cherry picked from commit 4c1aa64b4d804e77dfaa8d53e5ef699fcced4b18)
Fixes: aaecfecdcde5 ("kernel: bump kernel 4.4 to version 4.4.139")
kernel: ext4: fix check to prevent initializing reserved inodes 2018-08-09T21:17:09+00:00 Matthias Schiffer mschiffer@universe-factory.net 2018-08-09T20:45:26+00:00 0a2c984222d03d940c52c3675849dd6398b34e64 The broken check would detect a newly generated root filesystem as corrupt under certain circumstances, in some cases actually currupting the it while trying to handle the error condition. This is a regression introduced in kernel 4.4.140. The 4.14.y stable series has already received this fix, while it is still pending for 4.4.y and 4.9.y. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> 
The broken check would detect a newly generated root filesystem as corrupt
under certain circumstances, in some cases actually currupting the it while
trying to handle the error condition.

This is a regression introduced in kernel 4.4.140. The 4.14.y stable series
has already received this fix, while it is still pending for 4.4.y and
4.9.y.

Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
kernel: bump kernel 4.4 to version 4.4.147 2018-08-09T21:17:09+00:00 Matthias Schiffer mschiffer@universe-factory.net 2018-08-09T18:25:38+00:00 91d209362b97fc1ff2ab931fe854c99f5a5aae73 target/linux/ar71xx/patches-4.4/103-MIPS-ath79-fix-register-address-in-ath79_ddr_wb_flus.patch has been applied upstream; the two deleted brcm2708 patches have been useless even before (as the second one only reverted the first one). Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net> 
target/linux/ar71xx/patches-4.4/103-MIPS-ath79-fix-register-address-in-ath79_ddr_wb_flus.patch
has been applied upstream; the two deleted brcm2708 patches have been
useless even before (as the second one only reverted the first one).

Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
sdk: include arch/arm/ Linux includes along with arch/arm64/ ones 2018-08-04T11:44:10+00:00 Jo-Philipp Wich jo@mein.io 2018-08-03T11:45:27+00:00 b7e3f10e801998781cf123b9c81c305004f03439 The Linux headers on arm64 architectures contain references to common arch/arm/ headers which were not bundled by the SDK so far. Check if we're packing the SDK for an arm64 target and if we do, also include arch/arm headers as well. Fixes FS#1725. Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit 4bb8a678e0e0eaf5c3651cc73f3b2c4cb1d267a2) 
The Linux headers on arm64 architectures contain references to common
arch/arm/ headers which were not bundled by the SDK so far.

Check if we're packing the SDK for an arm64 target and if we do, also
include arch/arm headers as well.

Fixes FS#1725.
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
(cherry picked from commit 4bb8a678e0e0eaf5c3651cc73f3b2c4cb1d267a2)
sdk: bundle usbip userspace sources 2018-08-04T11:44:10+00:00 Jo-Philipp Wich jo@mein.io 2018-08-01T07:11:17+00:00 d93ef3c8c8a22768ae33ad7c7ca603d12a5c88f8 Bundle the usbip utility sources shipped with the Linux kernel tree in order to allow the usbip packages from the package feed to build within the OpenWrt SDK. Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit d0e0b7049f88774e67c3d5ad6b573f7070e5f900) 
Bundle the usbip utility sources shipped with the Linux kernel tree in
order to allow the usbip packages from the package feed to build within
the OpenWrt SDK.

Signed-off-by: Jo-Philipp Wich <jo@mein.io>
(cherry picked from commit d0e0b7049f88774e67c3d5ad6b573f7070e5f900)
WDR4900v1 remove dt node for absent hw crypto. 2018-07-22T01:06:10+00:00 Tim Small tim@seoss.co.uk 2018-07-04T13:05:18+00:00 28d4e55432701a3db2068c357b515fc1b5e44794 The WDR4900v1 uses the P1040 SoC, so the device tree pulls in the definition for the related P1010 SoC. However, the P1040 lacks the CAAM/SEC4 hardware crypto accelerator which the P1010 device tree defines. If left defined, this causes the CAAM drivers (if present) to attempt to use the non-existent device, making various crypto-related operations (e.g. macsec and ipsec) fail. This commit overrides the incorrect dt node definition in the included file. See also: - https://bugs.openwrt.org/index.php?do=details&task_id=1262 - https://community.nxp.com/thread/338432#comment-474107 Signed-off-by: Tim Small <tim@seoss.co.uk> Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com> (cherry picked from commit e97aaf483c71fd5e3072ec2dce53354fc97357c9) 
The WDR4900v1 uses the P1040 SoC, so the device tree pulls in the
definition for the related P1010 SoC.  However, the P1040 lacks the
CAAM/SEC4 hardware crypto accelerator which the P1010 device tree
defines.  If left defined, this causes the CAAM drivers (if present) to
attempt to use the non-existent device, making various crypto-related
operations (e.g. macsec and ipsec) fail.

This commit overrides the incorrect dt node definition in the included
file.

See also:
 - https://bugs.openwrt.org/index.php?do=details&task_id=1262
 - https://community.nxp.com/thread/338432#comment-474107

Signed-off-by: Tim Small <tim@seoss.co.uk>
Signed-off-by: Yousong Zhou <yszhou4tech@gmail.com>
(cherry picked from commit e97aaf483c71fd5e3072ec2dce53354fc97357c9)
apm821xx: fix sata access freezes 2018-07-19T16:55:20+00:00 Christian Lamparter chunkeey@gmail.com 2018-07-16T20:56:35+00:00 aee5c53a8d68c9894cc2062db18ca7375af85b4a The original vendor's driver programmed the dma controller's AHB HPROT values to enable bufferable, privileged mode. This along with the "same priorty for both channels" fixes the freezes according to @takimata, @And.short, that have been reported on the forum by @ticerex. Furtheremore, @takimata reported that the patch also improved the performance of the HDDs considerably: |<https://forum.lede-project.org/t/wd-mybook-live-duo-two-disks/16195/55> |It seems your patch unleashed the full power of the SATA port. |Where I was previously hitting a really hard limit at around |82 MB/s for reading and 27 MB/s for writing, I am now getting this: | |root@OpenWrt:/mnt# time dd if=/dev/zero of=tempfile bs=1M count=1024 |1024+0 records in |1024+0 records out |real 0m 13.65s |user 0m 0.01s |sys 0m 11.89s | |root@OpenWrt:/mnt# time dd if=tempfile of=/dev/null bs=1M count=1024 |1024+0 records in |1024+0 records out |real 0m 8.41s |user 0m 0.01s |sys 0m 4.70s | |This means: 121 MB/s reading and 75 MB/s writing! | |[...] | |The drive is a WD Green WD10EARX taken from an older MBL Single. |I repeated the test a few times with even larger files to rule out |any caching, I'm still seeing the same great performance. OpenWrt is |now completely on par with the original MBL firmware's performance. Signed-off-by: Christian Lamparter <chunkeey@gmail.com> 
The original vendor's driver programmed the dma controller's
AHB HPROT values to enable bufferable, privileged mode. This
along with the "same priorty for both channels" fixes the
freezes according to @takimata, @And.short, that have been
reported on the forum by @ticerex.

Furtheremore, @takimata reported that the patch also improved
the performance of the HDDs considerably:
|<https://forum.lede-project.org/t/wd-mybook-live-duo-two-disks/16195/55>
|It seems your patch unleashed the full power of the SATA port.
|Where I was previously hitting a really hard limit at around
|82 MB/s for reading and 27 MB/s for writing, I am now getting this:
|
|root@OpenWrt:/mnt# time dd if=/dev/zero of=tempfile bs=1M count=1024
|1024+0 records in
|1024+0 records out
|real    0m 13.65s
|user    0m 0.01s
|sys     0m 11.89s
|
|root@OpenWrt:/mnt# time dd if=tempfile of=/dev/null bs=1M count=1024
|1024+0 records in
|1024+0 records out
|real    0m 8.41s
|user    0m 0.01s
|sys     0m 4.70s
|
|This means: 121 MB/s reading and 75 MB/s writing!
|
|[...]
|
|The drive is a WD Green WD10EARX taken from an older MBL Single.
|I repeated the test a few times with even larger files to rule out
|any caching, I'm still seeing the same great performance. OpenWrt is
|now completely on par with the original MBL firmware's performance.

Signed-off-by: Christian Lamparter <chunkeey@gmail.com>