Re: [OpenWrt-Devel] Any progress on R_ARM_THM_JUMP11 issues?
Looks as though in the end this is a binutils bug with -fvisibility=hidden. Details on https://sourceware.org/bugzilla/show_bug.cgi?id=12532#c9 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] wireguard: unknown relocation: 102 [ARMv7 Thumb-2]
Hey Rui, I fixed it! It turned out to be caused by -fvisibility=hidden undoing the effect of the binutils fix from a while back. Here's the patch that makes the problem go away: https://git.zx2c4.com/wireguard-linux-compat/commit/?id=178cdfffb99f2fd6fb4a5bfd2f9319461d93f53b This will be in the next compat release. Jason ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] [19.07] wireguard: bump to 1.0.20200611
This bump fixes breakage introduced by kernel commit 8ab8786f78c3fc930f9abf6d6d85e95567de4e1f, which is part of the 4.14.181 kernel bump, and backported ip6_dst_lookup_flow to 4.14. This breaks the older WireGuard version currently in 19.07. For reference, the compilation error is the one below: build_dir/target-x86_64_musl/linux-x86_64/wireguard-linux-compat-1.0.20200506/src/compat/compat.h:104:42: error: 'const struct ipv6_stub' has no member named 'ipv6_dst_lookup'; did you mean 'ipv6_dst_lookup_flow'? #define ipv6_dst_lookup_flow(a, b, c, d) ipv6_dst_lookup(a, b, , c) + (void *)0 ?: dst Changelogs below taken from the official release announcements. == Changes since v1.0.20200506 == This release aligns with the changes I sent to DaveM for 5.7-rc7 and were pushed to net.git about 45 minutes ago. * qemu: use newer iproute2 for gcc-10 * qemu: add -fcommon for compiling ping with gcc-10 These enable the test suite to compile with gcc-10. * noise: read preshared key while taking lock Matt noticed a benign data race when porting the Linux code to OpenBSD. * queueing: preserve flow hash across packet scrubbing * noise: separate receive counter from send counter WireGuard now works with fq_codel, cake, and other qdiscs that make use of skb->hash. This should significantly improve latency spikes related to buffer bloat. Here's a before and after graph from some data Toke measured: https://data.zx2c4.com/removal-of-buffer-bloat-in-wireguard.png * compat: support RHEL 8 as 8.2, drop 8.1 support * compat: support CentOS 8 explicitly * compat: RHEL7 backported the skb hash renamings The usual RHEL churn. * compat: backport renamed/missing skb hash members The new support for fq_codel and friends meant more backporting work. * compat: ip6_dst_lookup_flow was backported to 4.14, 4.9, and 4.4 == Changes since v1.0.20200611 == * qemu: always use cbuild gcc rather than system gcc * qemu: remove -Werror in order to build ancient kernels better * qemu: patch kernels that rely on ancient make * qemu: force 2MB pages for binutils 2.31 * qemu: use cbuild gcc for avx512 exclusion * qemu: add extra fill in idt handler for newer binutils * qemu: support fetching kernels for arbitrary URLs * qemu: patch in UTS_UBUNTU_RELEASE_ABI for Ubuntu detection * qemu: work around broken centos8 kernel * qemu: mark per_cpu_load_addr as static for gcc-10 Our qemu test suite can now handle more kernels and more compilers. Scroll down to the bottom of https://www.wireguard.com/build-status/ to see the expanded array of kernels we now test against, including some distro kernels. * compat: widen breadth of integer constants * compat: widen breadth of memzero_explicit backport * compat: backport skb_scrub_packet to 3.11 * compat: widen breadth of prandom_u32_max backport * compat: narrow the breadth of iptunnel_xmit backport * compat: backport iptunnel_xmit to 3.11 With the expanded qemu test suite, it was possible to expand our list of mainline kernels, so the backport compat layer is now more precise. * compat: ubuntu appears to have backported ipv6_dst_lookup_flow * compat: bionic-hwe-5.0/disco kernel backported skb_reset_redirect and ipv6 flow Ubuntu kernels changed recently, so this ensures we can compile with the latest Ubuntu releases. * compat: remove stale suse support Signed-off-by: Stijn Segers --- 4.14.184 hasn't made its way into openwrt-19.07 yet but I bumped into this ip6_dst_lookup_flow issue with the .184 bump in Koen's tree. --- package/network/services/wireguard/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/package/network/services/wireguard/Makefile b/package/network/services/wireguard/Makefile index 69c9767b22..710038732b 100644 --- a/package/network/services/wireguard/Makefile +++ b/package/network/services/wireguard/Makefile @@ -11,12 +11,12 @@ include $(INCLUDE_DIR)/kernel.mk PKG_NAME:=wireguard -PKG_VERSION:=1.0.20200506 +PKG_VERSION:=1.0.20200611 PKG_RELEASE:=1 PKG_SOURCE:=wireguard-linux-compat-$(PKG_VERSION).tar.xz PKG_SOURCE_URL:=https://git.zx2c4.com/wireguard-linux-compat/snapshot/ -PKG_HASH:=98a99f2b825a82d57a7213e666f1ee4f7cc02bddb09bf4908b4b09447a8f121e +PKG_HASH:=9b0478c3b1f3a7b488916e632e2fcbb1383bb1a2ef294489858ce2ba1da3246d PKG_LICENSE:=GPL-2.0 PKG_LICENSE_FILES:=COPYING -- 2.20.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq: fritz7312: set maximum speed to 100 mbit on 5.4
> -Original Message- > From: Martin Blumenstingl [mailto:martin.blumensti...@googlemail.com] > Sent: Donnerstag, 18. Juni 2020 22:26 > To: Adrian Schmutzler > Cc: openwrt-devel@lists.openwrt.org; Alexander Couzens > Subject: Re: [OpenWrt-Devel] [PATCH] lantiq: fritz7312: set maximum speed > to 100 mbit on 5.4 > > Hi Adrian, > > On Thu, Jun 18, 2020 at 11:49 AM Adrian Schmutzler > wrote: > > > > The fritz 7312 does not support 1000 gbit. Advertising it makes it > > worse. Some NIC will change to 1000 gibt and turn off and on again for > > ever. > > > > The previous patch in 36f628910b8b was only applied to the 4.19 file. > according to [0] the 7312 has a 10/100Mbit/s Atheros AR8030-A PHY. > Do you know why it's advertising Gbit/s capabilities nevertheless? > > I won't say "no" to this patch > If it's a hardware issue then more boarding will benefit from a fix in the > ar803x PHY driver. Hi, I don't have any clue at all about the problem itself. I just found the inconsistency and want to align 4.19 and 5.4, as currently it is effectively a regression. If you want to address this differently, go for it, but don't ask me anything about it ;-) Best Adrian > > > Best regards, > Martin > > > [0] https://boxmatrix.info/wiki/FRITZ!Box_7312 openpgp-digital-signature.asc Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] lantiq: fritz7312: set maximum speed to 100 mbit on 5.4
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- Hi Adrian, On Thu, Jun 18, 2020 at 11:49 AM Adrian Schmutzler wrote: > > The fritz 7312 does not support 1000 gbit. Advertising it makes it > worse. Some NIC will change to 1000 gibt and turn off and on again for > ever. > > The previous patch in 36f628910b8b was only applied to the 4.19 file. according to [0] the 7312 has a 10/100Mbit/s Atheros AR8030-A PHY. Do you know why it's advertising Gbit/s capabilities nevertheless? I won't say "no" to this patch If it's a hardware issue then more boarding will benefit from a fix in the ar803x PHY driver. Best regards, Martin [0] https://boxmatrix.info/wiki/FRITZ!Box_7312 --- End Message --- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Merged: hostapd: fix compilation of wpa_supplicant
Merged into my staging tree at http://git.openwrt.org/?p=openwrt/staging/jow.git. Thank you! ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH luci] luci-mod-system: use ubus method for reboot
From: Rafał Miłecki
It's more generic & convenient than hardcoding /sbin/reboot executable
path. procd provides "reboot" method since 2016.
Signed-off-by: Rafał Miłecki
---
.../luci-static/resources/view/system/reboot.js | 13 ++---
.../root/usr/share/rpcd/acl.d/luci-mod-system.json | 3 ++-
2 files changed, 12 insertions(+), 4 deletions(-)
diff --git
a/modules/luci-mod-system/htdocs/luci-static/resources/view/system/reboot.js
b/modules/luci-mod-system/htdocs/luci-static/resources/view/system/reboot.js
index 3b9f450fc..249247bab 100644
--- a/modules/luci-mod-system/htdocs/luci-static/resources/view/system/reboot.js
+++ b/modules/luci-mod-system/htdocs/luci-static/resources/view/system/reboot.js
@@ -1,9 +1,16 @@
'use strict';
'require view';
'require fs';
+'require rpc';
'require ui';
'require uci';
+var callReboot = rpc.declare({
+ object: 'system',
+ method: 'reboot',
+ expect: { result: 0 }
+});
+
return view.extend({
load: function() {
return uci.changes();
@@ -31,9 +38,9 @@ return view.extend({
},
handleReboot: function(ev) {
- return fs.exec('/sbin/reboot').then(function(res) {
- if (res.code != 0) {
- L.ui.addNotification(null, E('p', _('The reboot
command failed with code %d').format(res.code)));
+ return callReboot().then(function(res) {
+ if (res != 0) {
+ L.ui.addNotification(null, E('p', _('The reboot
command failed with code %d').format(res)));
L.raise('Error', 'Reboot failed');
}
diff --git
a/modules/luci-mod-system/root/usr/share/rpcd/acl.d/luci-mod-system.json
b/modules/luci-mod-system/root/usr/share/rpcd/acl.d/luci-mod-system.json
index b29ddb8f4..38ff98dee 100644
--- a/modules/luci-mod-system/root/usr/share/rpcd/acl.d/luci-mod-system.json
+++ b/modules/luci-mod-system/root/usr/share/rpcd/acl.d/luci-mod-system.json
@@ -160,7 +160,8 @@
"/sbin/reboot": [ "exec" ]
},
"ubus": {
- "file": [ "exec" ]
+ "file": [ "exec" ],
+ "system": [ "reboot" ]
}
}
}
--
2.26.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [RFC PATCH v2] mvebu: compile the kernel in Thumb-2 mode for ARMv7 targets
(Sending as RFC due to the note below.) The Thumb-2 instruction set generates denser code, allowing for more efficient use of the cache and consequently higher execution performance. Vmlinux (uncompressed) size comparison for my personal configuration (Linux 5.4.46, compiled with gcc 9.3.0 and binutils 2.34): Pure ARM: 24243392 bytes Thumb-2: 22102716 bytes NOTE: This requires enabling a linker bug workaround to avoid the emission of R_ARM_THM_JUMP11 relocations [1] in modules, which the kernel doesn't support. Since this effectively implies -fno-optimize-sibling-calls [2], we're generating suboptimal code. While compat (and in-tree) modules load and run correctly without this workaround, WireGuard fails to load with an unknown relocation 102 error. [1] https://static.docs.arm.com/ihi0044/e/IHI0044E_aaelf.pdf (page 28) [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/Makefile?h=linux-5.4.y#n129 Signed-off-by: Rui Salvaterra --- target/linux/mvebu/cortexa9/config-5.4 | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 target/linux/mvebu/cortexa9/config-5.4 diff --git a/target/linux/mvebu/cortexa9/config-5.4 b/target/linux/mvebu/cortexa9/config-5.4 new file mode 100644 index 00..6aff77fda7 --- /dev/null +++ b/target/linux/mvebu/cortexa9/config-5.4 @@ -0,0 +1,2 @@ +CONFIG_THUMB2_AVOID_R_ARM_THM_JUMP11=y +CONFIG_THUMB2_KERNEL=y -- 2.27.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [RFC PATCH] mvebu: compile the kernel in Thumb-2 mode for ARMv7 targets
Please ignore this one, I'll send an updated patch shortly (only for 5.4, which I've tested). On Wed, 17 Jun 2020 at 18:37, Rui Salvaterra wrote: > > (Sending as RFC due to the note below.) > > The Thumb-2 instruction set generates denser code, allowing for more efficient > use of the cache and consequently higher execution performance. > > NOTE: This requires enabling a linker workaround to avoid the emission of > R_ARM_THM_JUMP11 relocations [1] in modules, which the kernel doesn't support. > Since this effectively implies -fno-optimize-sibling-calls [2], we're > generating > suboptimal code. While compat modules load and run correctly without this > workaround, WireGuard fails to load with an unknown relocation 102 error. > > [1] https://static.docs.arm.com/ihi0044/e/IHI0044E_aaelf.pdf (page 28) > [2] > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm/Makefile?h=linux-5.4.y#n129 > > Signed-off-by: Rui Salvaterra > --- > target/linux/mvebu/cortexa9/config-default | 2 ++ > 1 file changed, 2 insertions(+) > create mode 100644 target/linux/mvebu/cortexa9/config-default > > diff --git a/target/linux/mvebu/cortexa9/config-default > b/target/linux/mvebu/cortexa9/config-default > new file mode 100644 > index 00..6aff77fda7 > --- /dev/null > +++ b/target/linux/mvebu/cortexa9/config-default > @@ -0,0 +1,2 @@ > +CONFIG_THUMB2_AVOID_R_ARM_THM_JUMP11=y > +CONFIG_THUMB2_KERNEL=y > -- > 2.27.0 > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH v2 0/3] build: Avoid 'Argument list too long' error
Hello,
Thank you for your patches, Eneas! We (for Turris routers) experienced
the same that you are describing once we did an update on build servers
from Debian Stretch to Debian Buster. It is present also for OpenWrt
19.07, where we were able to see it first because currently OpenWrt
master we are not able to compile because hostapd fails. More about
it https://lists.infradead.org/pipermail/openwrt-devel/2020-June/023976.html
So all these tested patches were tested and feel free to add my:
Tested-by: Josef Schlehofer
Regards,
Josef
On 20. 02. 20 22:29, Eneas U de Queiroz wrote:
> TLDR for those who have read v1: I've come up with a good-enough, but
> not perfect wildcard pattern, and added it in a separate commit.
>
> After building all of the luci packages with all of the translations,
> if I either run:
> 'make package/luci/clean' or 'make package/luci/compile', I get:
> make[2]: execvp: /usr/bin/env: Argument list too long
> make[2]: *** [../../luci.mk:285: luci-clean] Error 127
>
> This is caused by the call to scripts/ipkg-remove with a list of over
> 2,300 packages matching a luci* wildcard:
> $ ll bin/packages/arm_cortex-a9_vfpv3/luci/luci*.ipk | wc -l
> 2307
>
> My first attempt to circumvent this was using xargs. However, using
> echo from the Makefile results in make calling the shell with the same
> 2,307 file names. The solution is to have make write the list to a file
> and then feed it to xargs.
>
> To avoid creating a file every time, xargs is only used when the number
> of files is >=512.
>
> As an optimization, to avoid calling wildcard twice, I've defined a
> RemoveOpkgPackageFiles function, and added the check for an empty list
> there, so that the call to opkg_package_files would only be done when
> the new function was called.
>
> I've put them in separate commits to ease an eventual reversal or
> rejection.
>
> If we change the wildcard pattern that selects the files, we can
> eliminate the problems with xargs, and avoid 4,612 runs of 'tar -Ozxf'
> when making package/luci/compile.
>
> There is a caveat; it will not remove the .ipk file if the version of
> a package whose name ends in a digit (e.g. nghttp2) that was currently
> built with an ABI_VERSION, but the version of the new build does not
> have an ABI_VERSION. Then, make package/nghttp2/clean will not remove
> the old ipk file.
>
> I consider this extremely minor. Nonetheless, I will leave the
> intermediate commit, since it works in 100% of the cases, making it
> easier to revert this. If I should rather squash them, let me know
> which commits should be kept and I'll send a v3.
>
> This was compile-tested for mvebu, and checked by adding $(info ...)
> tracers to the new functions and to opkg_package_files in
> include/feeds.mk.
>
> To check how many ipk files each package was selecting with the new
> wildcard, I've run the following script in a directory containing all
> packages that I've build for mvebu:
>
> #!/bin/bash
> total=0
> packages=0
> for f in *.ipk; do
> PKG=$(tar -Ozxf "$f" ./control.tar.gz | tar -Ozxf - ./control \
> | sed -ne '/^Package:/{s,.*: ,,; p}')
> SRC=$(tar -Ozxf "$f" ./control.tar.gz | tar -Ozxf - ./control \
> | sed -ne '/^SourceName:/{s,.*: ,,; p}')
> if [ "${SRC}" = "${PKG}" ]; then
> files="${PKG}[^a-z-]*_*.ipk"
> else
> case "${SRC}" in
>*[0-9] )
> files="${SRC}*_*.ipk"
> ;;
>* )
> files="${SRC}[^a-z-]*_*.ipk"
> esac
> fi
> n=$(echo ${files} | wc -w)
> if [ "$n" -ne 1 ]; then
> echo pkg=${SRC} - n=${n}
> ls -1 ${files}
> fi
> ((total = total + n))
> ((packages++))
> done
> echo Total Packages=${packages}. Total lookups=${total}
>
> If you want to see the old wildcard, always use `files=${SRC}*_*.ipk`.
>
> Before the change:
> Total Packages=8213. Total lookups=16689
> After:
> Total Packages=8213. Total lookups=8838
>
> ChangeLog:
>
> v1->v2:
> * Renamed the new functions using lowercase and underscores
> * Used '< file' instead of 'cat file |' to pass the files to xargs
> * Added a commit changing the wildcard pattern, reverting the use of
> xargs.
>
> Eneas U de Queiroz (3):
> build: package-ipkg: avoid calling wildcard twice
> build: call ipkg-remove using xargs if #args>=512
> build: reduce number of files passed to ipk-remove
>
> include/package-ipkg.mk | 17 +++--
> 1 file changed, 15 insertions(+), 2 deletions(-)
>
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] lantiq: fritz7312: set maximum speed to 100 mbit on 5.4
The fritz 7312 does not support 1000 gbit. Advertising it makes it
worse. Some NIC will change to 1000 gibt and turn off and on again for
ever.
The previous patch in 36f628910b8b was only applied to the 4.19 file.
Cc: Alexander Couzens
Signed-off-by: Adrian Schmutzler
---
.../files-5.4/arch/mips/boot/dts/lantiq/ar9_avm_fritz7312.dts| 1 +
1 file changed, 1 insertion(+)
diff --git
a/target/linux/lantiq/files-5.4/arch/mips/boot/dts/lantiq/ar9_avm_fritz7312.dts
b/target/linux/lantiq/files-5.4/arch/mips/boot/dts/lantiq/ar9_avm_fritz7312.dts
index aa825abd9f..0f635127f8 100644
---
a/target/linux/lantiq/files-5.4/arch/mips/boot/dts/lantiq/ar9_avm_fritz7312.dts
+++
b/target/linux/lantiq/files-5.4/arch/mips/boot/dts/lantiq/ar9_avm_fritz7312.dts
@@ -108,6 +108,7 @@
phy0: ethernet-phy@0 {
reg = <0>;
reset-gpios = < 34 GPIO_ACTIVE_LOW>;
+ max-speed = <100>;
};
};
};
--
2.20.1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH 2/2] mvebu: consolidate DTS files
The DTS files in files-4.19 and files-5.4 are exactly identical
except for one file (armada-3720-uDPU.dts), which is only present
for 4.19, as it has been upstreamed before 5.4.
Since there is no point in maintaining all these identical files
twice, this patch moves them to the "files" directory, only keeping
the named exception to files-4.19.
Signed-off-by: Adrian Schmutzler
---
.../boot/dts/armada-370-buffalo-ls421de.dts | 360 --
.../arm/boot/dts/armada-385-linksys-venom.dts | 213 ---
.../marvell/armada-3720-espressobin-emmc.dts | 28 --
.../armada-3720-espressobin-v7-emmc.dts | 43 ---
.../marvell/armada-3720-espressobin-v7.dts| 31 --
.../dts/marvell/armada-3720-gl-mv1000.dts | 162
.../boot/dts/armada-370-buffalo-ls421de.dts | 0
.../arm/boot/dts/armada-385-linksys-venom.dts | 0
.../marvell/armada-3720-espressobin-emmc.dts | 0
.../armada-3720-espressobin-v7-emmc.dts | 0
.../marvell/armada-3720-espressobin-v7.dts| 0
.../dts/marvell/armada-3720-gl-mv1000.dts | 0
12 files changed, 837 deletions(-)
delete mode 100644
target/linux/mvebu/files-5.4/arch/arm/boot/dts/armada-370-buffalo-ls421de.dts
delete mode 100644
target/linux/mvebu/files-5.4/arch/arm/boot/dts/armada-385-linksys-venom.dts
delete mode 100644
target/linux/mvebu/files-5.4/arch/arm64/boot/dts/marvell/armada-3720-espressobin-emmc.dts
delete mode 100644
target/linux/mvebu/files-5.4/arch/arm64/boot/dts/marvell/armada-3720-espressobin-v7-emmc.dts
delete mode 100644
target/linux/mvebu/files-5.4/arch/arm64/boot/dts/marvell/armada-3720-espressobin-v7.dts
delete mode 100644
target/linux/mvebu/files-5.4/arch/arm64/boot/dts/marvell/armada-3720-gl-mv1000.dts
rename target/linux/mvebu/{files-4.19 =>
files}/arch/arm/boot/dts/armada-370-buffalo-ls421de.dts (100%)
rename target/linux/mvebu/{files-4.19 =>
files}/arch/arm/boot/dts/armada-385-linksys-venom.dts (100%)
rename target/linux/mvebu/{files-4.19 =>
files}/arch/arm64/boot/dts/marvell/armada-3720-espressobin-emmc.dts (100%)
rename target/linux/mvebu/{files-4.19 =>
files}/arch/arm64/boot/dts/marvell/armada-3720-espressobin-v7-emmc.dts (100%)
rename target/linux/mvebu/{files-4.19 =>
files}/arch/arm64/boot/dts/marvell/armada-3720-espressobin-v7.dts (100%)
rename target/linux/mvebu/{files-4.19 =>
files}/arch/arm64/boot/dts/marvell/armada-3720-gl-mv1000.dts (100%)
diff --git
a/target/linux/mvebu/files-5.4/arch/arm/boot/dts/armada-370-buffalo-ls421de.dts
b/target/linux/mvebu/files-5.4/arch/arm/boot/dts/armada-370-buffalo-ls421de.dts
deleted file mode 100644
index 6b8a964ab3..00
---
a/target/linux/mvebu/files-5.4/arch/arm/boot/dts/armada-370-buffalo-ls421de.dts
+++ /dev/null
@@ -1,360 +0,0 @@
-// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
-/*
- * Device Tree file for Buffalo LinkStation LS421DE
- *
- * Copyright (C) 2020 Daniel González Cabanelas
- */
-
-/dts-v1/;
-
-#include "armada-370.dtsi"
-#include "mvebu-linkstation-fan.dtsi"
-#include
-#include
-
-/ {
- model = "Buffalo LinkStation LS421DE";
- compatible = "buffalo,ls421de", "marvell,armada370",
"marvell,armada-370-xp";
-
- aliases {
- led-boot = _boot;
- led-failsafe = _failsafe;
- led-running = _power;
- led-upgrade = _upgrade;
- };
-
- chosen {
- bootargs = "console=ttyS0,115200 earlyprintk noinitrd
rootfstype=squashfs";
- stdout-path = "serial0:115200n8";
- append-rootblock = "nullparameter="; /* override the bootloader
args */
- };
-
- memory {
- device_type = "memory";
- reg = <0x 0x2000>; /* 512 MB */
- };
-
- soc {
- ranges = ;
- };
-
- gpio_fan {
- gpios = < 13 GPIO_ACTIVE_HIGH
-14 GPIO_ACTIVE_HIGH>;
- alarm-gpios = < 10 GPIO_ACTIVE_HIGH>;
- };
-
- gpio_keys {
- compatible = "gpio-keys";
- #address-cells = <1>;
- #size-cells = <0>;
- pinctrl-0 = <_hdd_present _buttons>;
- pinctrl-names = "default";
-
- hdd1-present {
- label = "HDD1 Present";
- linux,code = ;
- gpios = < 11 GPIO_ACTIVE_LOW>;
- };
-
- hdd2-present {
- label = "HDD2 Present";
- linux,code = ;
- gpios = < 12 GPIO_ACTIVE_LOW>;
-
- };
-
- power {
- label = "Power Switch";
- linux,code = ;
- linux,input-type = ;
- gpios = < 15 GPIO_ACTIVE_LOW>;
- };
-
- function {
- label = "Function Button";
- linux,code = ;
- gpios = < 16
Re: [OpenWrt-Devel] [PATCH] kernel: bump 5.4 to 5.4.47
On 18.06.20 10:52, Kevin 'ldir' Darbyshire-Bryant wrote: On 18 Jun 2020, at 08:58, Koen Vandeputte wrote: On 18.06.20 08:50, Kevin Darbyshire-Bryant wrote: Refreshed patches. Run tested: x86/64 (apu2) Signed-off-by: Kevin Darbyshire-Bryant --- I've got the bumps in my staging already sinds a day or 2 :-) AFAIUI 5.4.47 was release 17 hours ago, a few hours after ynezz committed 5.4.46 - I think. ah right .. mine was .46 got to rebase again for the other bumps .. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] kernel: bump 5.4 to 5.4.47
> On 18 Jun 2020, at 08:58, Koen Vandeputte > wrote: > > > On 18.06.20 08:50, Kevin Darbyshire-Bryant wrote: >> Refreshed patches. >> >> Run tested: x86/64 (apu2) >> >> Signed-off-by: Kevin Darbyshire-Bryant >> --- > > > I've got the bumps in my staging already sinds a day or 2 :-) > AFAIUI 5.4.47 was release 17 hours ago, a few hours after ynezz committed 5.4.46 - I think. signature.asc Description: Message signed with OpenPGP ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] kernel: bump 5.4 to 5.4.47
On 18.06.20 08:50, Kevin Darbyshire-Bryant wrote: Refreshed patches. Run tested: x86/64 (apu2) Signed-off-by: Kevin Darbyshire-Bryant --- I've got the bumps in my staging already sinds a day or 2 :-) ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] kernel: bump 5.4 to 5.4.47
Refreshed patches.
Run tested: x86/64 (apu2)
Signed-off-by: Kevin Darbyshire-Bryant
---
include/kernel-version.mk | 4 ++--
...653-spi-Force-CS_HIGH-if-GPIO-descriptors-are-used.patch | 4 ++--
...QUASH-spi-Demote-SPI_CS_HIGH-warning-to-KERN_DEBUG.patch | 2 +-
.../825-v5.8-spi-rb4xx-null-pointer-bug-fix.patch | 6 ++
8-spi-rb4xx-update-driver-to-be-device-tree-aware.patch | 6 ++
target/linux/generic/hack-5.4/221-module_exports.patch | 2 +-
target/linux/generic/hack-5.4/902-debloat_proc.patch| 4 ++--
.../generic/pending-5.4/203-kallsyms_uncompressed.patch | 2 +-
...-allow-rejecting-with-source-address-failed-policy.patch | 2 +-
...c-sdhci-sdhci-msm-use-sdhci_set_clock-instead-of-s.patch | 2 +-
.../linux/x86/patches-5.4/200-pcengines-apu2-reboot.patch | 2 +-
11 files changed, 16 insertions(+), 20 deletions(-)
diff --git a/include/kernel-version.mk b/include/kernel-version.mk
index fa62ccbe2a..f69b8977c5 100644
--- a/include/kernel-version.mk
+++ b/include/kernel-version.mk
@@ -8,11 +8,11 @@ endif
LINUX_VERSION-4.14 = .180
LINUX_VERSION-4.19 = .123
-LINUX_VERSION-5.4 = .46
+LINUX_VERSION-5.4 = .47
LINUX_KERNEL_HASH-4.14.180 =
444ef973d9b6a6ea174e4a9086f0aea980d8575d13302e431ad688f22e27ed0e
LINUX_KERNEL_HASH-4.19.123 =
a79914d31a8d8c6b0e2bb0f2b143d615fe8a6c4dd2e0f36e97aa20efd69a993f
-LINUX_KERNEL_HASH-5.4.46 =
30074ff2f1a2498da391fad73fc0efaa2256416a08fff8835069b1c59ab31b8e
+LINUX_KERNEL_HASH-5.4.47 =
970b9d393d9a8d45eafdec9c6ab0d9880c20c703eeb9b0ac409892c8bc418d6c
remove_uri_prefix=$(subst git://,,$(subst http://,,$(subst https://,,$(1
sanitize_uri=$(call qstrip,$(subst @,_,$(subst :,_,$(subst .,_,$(subst
-,_,$(subst /,_,$(1)))
diff --git
a/target/linux/bcm27xx/patches-5.4/950-0653-spi-Force-CS_HIGH-if-GPIO-descriptors-are-used.patch
b/target/linux/bcm27xx/patches-5.4/950-0653-spi-Force-CS_HIGH-if-GPIO-descriptors-are-used.patch
index 43d10486de..9c090a0597 100644
---
a/target/linux/bcm27xx/patches-5.4/950-0653-spi-Force-CS_HIGH-if-GPIO-descriptors-are-used.patch
+++
b/target/linux/bcm27xx/patches-5.4/950-0653-spi-Force-CS_HIGH-if-GPIO-descriptors-are-used.patch
@@ -23,7 +23,7 @@ Signed-off-by: Phil Elwell
--- a/drivers/spi/spi.c
+++ b/drivers/spi/spi.c
-@@ -3032,6 +3032,7 @@ static int __spi_validate_bits_per_word(
+@@ -3033,6 +3033,7 @@ static int __spi_validate_bits_per_word(
*/
int spi_setup(struct spi_device *spi)
{
@@ -31,7 +31,7 @@ Signed-off-by: Phil Elwell
unsignedbad_bits, ugly_bits;
int status;
-@@ -3049,6 +3050,14 @@ int spi_setup(struct spi_device *spi)
+@@ -3050,6 +3051,14 @@ int spi_setup(struct spi_device *spi)
(SPI_TX_DUAL | SPI_TX_QUAD | SPI_TX_OCTAL |
SPI_RX_DUAL | SPI_RX_QUAD | SPI_RX_OCTAL)))
return -EINVAL;
diff --git
a/target/linux/bcm27xx/patches-5.4/950-0697-SQUASH-spi-Demote-SPI_CS_HIGH-warning-to-KERN_DEBUG.patch
b/target/linux/bcm27xx/patches-5.4/950-0697-SQUASH-spi-Demote-SPI_CS_HIGH-warning-to-KERN_DEBUG.patch
index 2be5524a07..617873ce42 100644
---
a/target/linux/bcm27xx/patches-5.4/950-0697-SQUASH-spi-Demote-SPI_CS_HIGH-warning-to-KERN_DEBUG.patch
+++
b/target/linux/bcm27xx/patches-5.4/950-0697-SQUASH-spi-Demote-SPI_CS_HIGH-warning-to-KERN_DEBUG.patch
@@ -15,7 +15,7 @@ Signed-off-by: Phil Elwell
--- a/drivers/spi/spi.c
+++ b/drivers/spi/spi.c
-@@ -3044,8 +3044,8 @@ int spi_setup(struct spi_device *spi)
+@@ -3045,8 +3045,8 @@ int spi_setup(struct spi_device *spi)
if (ctlr->use_gpio_descriptors && ctlr->cs_gpiods &&
ctlr->cs_gpiods[spi->chip_select] && !(spi->mode & SPI_CS_HIGH)) {
diff --git
a/target/linux/generic/backport-5.4/825-v5.8-spi-rb4xx-null-pointer-bug-fix.patch
b/target/linux/generic/backport-5.4/825-v5.8-spi-rb4xx-null-pointer-bug-fix.patch
index 5d762c571c..71e26d50da 100644
---
a/target/linux/generic/backport-5.4/825-v5.8-spi-rb4xx-null-pointer-bug-fix.patch
+++
b/target/linux/generic/backport-5.4/825-v5.8-spi-rb4xx-null-pointer-bug-fix.patch
@@ -20,11 +20,9 @@ Signed-off-by: Christopher Hill
drivers/spi/spi-rb4xx.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
-diff --git a/drivers/spi/spi-rb4xx.c b/drivers/spi/spi-rb4xx.c
-index 4c9620e0d18c..17e1a77dc132 100644
--- a/drivers/spi/spi-rb4xx.c
+++ b/drivers/spi/spi-rb4xx.c
-@@ -158,6 +158,11 @@ static int rb4xx_spi_probe(struct platform_device *pdev)
+@@ -158,6 +158,11 @@ static int rb4xx_spi_probe(struct platfo
master->transfer_one = rb4xx_transfer_one;
master->set_cs = rb4xx_set_cs;
@@ -36,7 +34,7 @@ index 4c9620e0d18c..17e1a77dc132 100644
err = devm_spi_register_master(>dev, master);
if (err) {
dev_err(>dev, "failed to register SPI master\n");
-@@ -168,11 +173,6 @@ static int rb4xx_spi_probe(struct platform_device *pdev)
+@@ -168,11 +173,6 @@ static int rb4xx_spi_probe(struct platfo
