Re: [OpenWrt-Devel] Ath10k: How is the interface mac address set?

2020-04-01 Thread Hannu Nyman
Kevin Mahoney wrote at Wed Apr 1 20:15:21 PDT 2020: > I'm working with an IPQ8065 based board with dual QCA9984s. I have it up and running but the wireless interfaces mac address is garbage. > "00:03:7f:12:34:56" to be exact. I haven't been able to find the magic that reads and sets the proper

[OpenWrt-Devel] Ath10k: How is the interface mac address set?

2020-04-01 Thread Kevin Mahoney
I'm working with an IPQ8065 based board with dual QCA9984s. I have it up and running but the wireless interfaces mac address is garbage. "00:03:7f:12:34:56" to be exact. I haven't been able to find the magic that reads and sets the proper address from non-volatile memory. Any pointers? Regards, *

Re: [OpenWrt-Devel] [PATCH 1/3] ipq806x: remove support for kernel 4.14

2020-04-01 Thread Stefan Lippers-Hollmann
Hi On 2020-04-02, Adrian Schmutzler wrote: > This target has been on kernel 4.19 for several months [1] and > already uses kernel 5.4 as testing kernel. Therefore, it should > not be necessary to keep support for kernel 4.14 as well. > > [1] 2a82e0e1ca0f ("ipq806x: switch to 4.19 kernel version")

[OpenWrt-Devel] [PATCH 2/3] mediatek: remove support for kernel 4.14

2020-04-01 Thread Adrian Schmutzler
This target has been on kernel 4.19 for a few months [1,2] and already uses kernel 5.4 as testing kernel. Therefore, it should not be necessary to keep support for kernel 4.14 as well. [1] 09fe0c847dd3 ("mediatek: add mt7629 subtarget with rfb image") [2] 01c8f2e97cc6 ("mediatek: bump to v4.19")

[OpenWrt-Devel] [PATCH 1/3] ipq806x: remove support for kernel 4.14

2020-04-01 Thread Adrian Schmutzler
This target has been on kernel 4.19 for several months [1] and already uses kernel 5.4 as testing kernel. Therefore, it should not be necessary to keep support for kernel 4.14 as well. [1] 2a82e0e1ca0f ("ipq806x: switch to 4.19 kernel version") Signed-off-by: Adrian Schmutzler --- target/linux/

[OpenWrt-Devel] [PATCH 3/3] cns3xx: remove support for kernel 4.14

2020-04-01 Thread Adrian Schmutzler
This target has been on kernel 4.19 for nine months now [1], and has had testing support for even longer [2]. This should be long enough to drop support for kernel 4.14. [1] 545bfbc3a922 ("cns3xxx: switch to kernel 4.19") [2] c6bebe1a9496 ("cns3xxx: add support for kernel 4.19") Signed-off-by: Ad

[OpenWrt-Devel] [PATCH 0/3] drop 4.14 support on some targets

2020-04-01 Thread Adrian Schmutzler
This drops support for kernel 4.14 on some additional targets where we have had two other versions for some time or where 4.19 support is quite old: - ipq806x - mediatek - cns3xxx Adrian Schmutzler (3): ipq806x: remove support for kernel 4.14 mediatek: remove support for kernel 4.14 cns3xx:

[OpenWrt-Devel] [PATCH 0/3] drop 4.14 support on some targets

2020-04-01 Thread Adrian Schmutzler
This drops support for kernel 4.14 on some additional targets where we have had two other versions for some time or where 4.19 support is quite old: - ipq806x - mediatek - cns3xxx Adrian Schmutzler (3): ipq806x: remove support for kernel 4.14 mediatek: remove support for kernel 4.14 cns3xx:

[OpenWrt-Devel] [PATCH] wireguard: bump to 1.0.20200401

2020-04-01 Thread Jason A. Donenfeld
Recent backports to 5.5 and 5.4 broke our compat layer. This release is to keep things running with the latest upstream stable kernels. Signed-off-by: Jason A. Donenfeld --- package/network/services/wireguard/Makefile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packag

Re: [OpenWrt-Devel] [PATCH v1 1/2] kmod-sched-cake: rename to kmod-sched-cake-oot

2020-04-01 Thread Kevin 'ldir' Darbyshire-Bryant
> On 1 Apr 2020, at 18:07, Hannu Nyman wrote: > > Kevin Darbyshire-Bryant kirjoitti 1.4.2020 klo 13.14: >> In preparation for dropping the out of tree cake module and using >> in tree cake from upstream, rename the package to kmod-sched-cake-oot >> (out of tree) >> >> Initially add a PROVIDES

Re: [OpenWrt-Devel] [PATCH v1 0/2] Moving to drop Out of tree cake

2020-04-01 Thread Hannu Nyman
Kevin Darbyshire-Bryant kirjoitti 1.4.2020 klo 13.14: Cake has been in upstream linux from 4.19 onward yet openwrt still builds a module from out of tree source. This patch set intends to drop the out of tree module for those versions of linux that contain an in-tree version + various backports

[OpenWrt-Devel] [PATCH] octeontx: switch to kernel 5.4

2020-04-01 Thread Tim Harvey
5.4 is stable on Gateworks Newport GW610x/GW620x/GW630x/GW640x Signed-off-by: Tim Harvey --- target/linux/octeontx/Makefile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/target/linux/octeontx/Makefile b/target/linux/octeontx/Makefile index 19a264d..67addbd 100644 --- a/ta

[OpenWrt-Devel] [PATCH] imx6: bootscript: use partition UUID for rootfs if possible

2020-04-01 Thread Tim Harvey
Specifying root filesystem by device is non-deterministic for several reasons: - USB device unmeration order is not garunteeed for USB storage devs - MMC devs ordering is determined by the instance of the MMC host controller including non-storage SDIO devices which can throw off numbering d

Re: [OpenWrt-Devel] [PATCH v1 1/2] kmod-sched-cake: rename to kmod-sched-cake-oot

2020-04-01 Thread Hannu Nyman
Kevin Darbyshire-Bryant kirjoitti 1.4.2020 klo 13.14: In preparation for dropping the out of tree cake module and using in tree cake from upstream, rename the package to kmod-sched-cake-oot (out of tree) Initially add a PROVIDES kmod-sched-cake so that package dependencies can be satisfied. Ult

Re: [OpenWrt-Devel] [PATCH] mvebu, tegra: make CPU subtype default to vfp3-d16

2020-04-01 Thread Petr Štetiar
Klaus Kudielka [2020-04-01 16:52:41]: Hi, > omap & sunxi/cortexa8 are both cortex-a8. good point, I've missed that. > So, tegra and mvebu/cortexa9 are the *only* targets with arm_cortex-a9_vfpv3 > (-d16) packages? Seems so. > If we switch both, like Tomasz did, arm_cortex-a9_vfpv3 would not

Re: [OpenWrt-Devel] [PATCH] mvebu, tegra: make CPU subtype default to vfp3-d16

2020-04-01 Thread Tomasz Maciej Nowak
W dniu 01.04.2020 o 16:52, Klaus Kudielka pisze: > Hi Petr & Tomasz, > >> In order to fix those issues Tomas in commit 2d61f8821c7c ("mvebu: >> cortexa9: correct cpu subtype") and commit 43d1d8851062 ("tegra: correct >> cpu subtype") changed the CPU subtype to explicit vfpv3-d16 which fixed >> the

Re: [OpenWrt-Devel] [PATCH v2] mvebu: add support for Buffalo LinkStation LS421DE

2020-04-01 Thread Tomasz Maciej Nowak
W dniu 29.03.2020 o 18:52, Daniel Gonzalez Cabanelas pisze: > Buffalo LinkStation LS421DE is a dual bay NAS, based on Marvell Armada 370 > > Hardware: >SoC: Marvell Armada-370 88F6707-A1 >CPU: Cortex-A9 1200 MHz, 1 core >Flash: SPI-NOR 1 MiB, NAND 512 MiB >RAM

Re: [OpenWrt-Devel] [PATCH] mvebu, tegra: make CPU subtype default to vfp3-d16

2020-04-01 Thread Petr Štetiar
Christian Lamparter [2020-04-01 15:43:40]: Hi Christian, > > > diff --git a/include/target.mk b/include/target.mk > > > index 9bd4c14936c1..94ea1a9e0001 100644 > > > --- a/include/target.mk > > > +++ b/include/target.mk > > > @@ -179,6 +179,9 @@ ifeq ($(DUMP),1) > > >endif > > >ifneq ($(

Re: [OpenWrt-Devel] [PATCH] mvebu, tegra: make CPU subtype default to vfp3-d16

2020-04-01 Thread Christian Lamparter
On Wednesday, 1 April 2020 15:17:31 CEST Tomasz Maciej Nowak wrote: > W dniu 31.03.2020 o 11:21, Petr Štetiar pisze: > > Armada 370 and Tegra2 processors have only 16 double-precision > > registers. The change introduced by commit 8dcc1087602e ("toolchain: > > ARM: Fix toolchain compilation for gcc

Re: [OpenWrt-Devel] [PATCH] mvebu, tegra: make CPU subtype default to vfp3-d16

2020-04-01 Thread Tomasz Maciej Nowak
W dniu 31.03.2020 o 11:21, Petr Štetiar pisze: > Armada 370 and Tegra2 processors have only 16 double-precision > registers. The change introduced by commit 8dcc1087602e ("toolchain: > ARM: Fix toolchain compilation for gcc 8.x") switched accidentally the > toolchain for mvebu cortexa9 subtarget to

Re: [OpenWrt-Devel] [PATCH] mvebu/cortexa9: use Linksys codename as PROFILE

2020-04-01 Thread mail
Hi, > > How about patching device's DTSes and include 'manufacturer,model' > there instead (in front of the existing ones)? Scripts in 'basic-files' would > also > need to be fixed but this way we save this (in my opinion) misuse of > 'DEVICE_ALT*'. > > Yes, that would be the easiest solution, n

Re: [OpenWrt-Devel] [PATCH] mvebu/cortexa9: use Linksys codename as PROFILE

2020-04-01 Thread Tomasz Maciej Nowak
W dniu 01.04.2020 o 14:15, Piotr Dymacz pisze: > Hi Tomasz, Paul, > > On 01.04.2020 14:03, Tomasz Maciej Nowak wrote: >> W dniu 01.04.2020 o 08:55, Piotr Dymacz pisze: >>> Hi Paul, >>> >>> On 01.04.2020 01:20, Paul Spooren wrote: The PROFILE names of mvebu/cortexa9/Linksys devices are based o

Re: [OpenWrt-Devel] [PATCH] mvebu/cortexa9: use Linksys codename as PROFILE

2020-04-01 Thread Piotr Dymacz
Hi Tomasz, Paul, On 01.04.2020 14:03, Tomasz Maciej Nowak wrote: W dniu 01.04.2020 o 08:55, Piotr Dymacz pisze: Hi Paul, On 01.04.2020 01:20, Paul Spooren wrote: The PROFILE names of mvebu/cortexa9/Linksys devices are based on the consumer names (like linksys_wrt1200ac) instead of the vendor

Re: [OpenWrt-Devel] [PATCH] mvebu/cortexa9: use Linksys codename as PROFILE

2020-04-01 Thread Tomasz Maciej Nowak
W dniu 01.04.2020 o 08:55, Piotr Dymacz pisze: > Hi Paul, > > On 01.04.2020 01:20, Paul Spooren wrote: >> The PROFILE names of mvebu/cortexa9/Linksys devices are based on the >> consumer names (like linksys_wrt1200ac) instead of the vendor codenames >> (like linksys_caiman) which are however used

Re: [OpenWrt-Devel] [PATCH] mvebu/cortexa9: use Linksys codename as PROFILE

2020-04-01 Thread Bjørn Mork
Paul Spooren writes: > -define Device/linksys_wrt1900acv2 > +define Device/linksys_cobra >$(call Device/linksys) > - DEVICE_MODEL := WRT1900AC > - DEVICE_VARIANT := v2 > + DEVICE_MODEL := Cobra >DEVICE_ALT0_VENDOR := Linksys > - DEVICE_ALT0_MODEL := Cobra > + DEVICE_ALT0_MODEL := WRT

[OpenWrt-Devel] [PATCH v1 2/2] kmod-sched-cake: switch to in-tree cake for 4.19+

2020-04-01 Thread Kevin Darbyshire-Bryant
Use in tree version of cake for kernels 4.19+ and backport features from later kernel versions to 4.19. Unfortunately PROVIDES dependency handling produces bogus circular dependency warnings so whilst this package and kmod-sched-cake-oot should be able to PROVIDE kmod-sched-cake this doesn't work.

[OpenWrt-Devel] [PATCH v1 0/2] Moving to drop Out of tree cake

2020-04-01 Thread Kevin Darbyshire-Bryant
Cake has been in upstream linux from 4.19 onward yet openwrt still builds a module from out of tree source. This patch set intends to drop the out of tree module for those versions of linux that contain an in-tree version + various backports of upstream enhancements. Unfortunately it's not as sim

[OpenWrt-Devel] [PATCH v1 1/2] kmod-sched-cake: rename to kmod-sched-cake-oot

2020-04-01 Thread Kevin Darbyshire-Bryant
In preparation for dropping the out of tree cake module and using in tree cake from upstream, rename the package to kmod-sched-cake-oot (out of tree) Initially add a PROVIDES kmod-sched-cake so that package dependencies can be satisfied. Ultimately this package will be removed when linux 4.14 is