[OpenWrt-Devel] [PATCH] ath79: harmonize ethernet-phy naming scheme

2020-01-27 Thread Adrian Schmutzler
A minority of ethernet-phy definitions seems to use numbers in label, name and reg property relatively random. This patch aligns their use to have the same numeric value for all of them. While at it, improve order of properties/add newlines for the ethX nodes where necessary. Signed-off-by: Adria

[OpenWrt-Devel] ath79: NAND bad eraseblocks in MikroTik RouterBOARD 922UAGS-5HPacD

2020-01-27 Thread Roger Pueyo Centelles | Guifi.net via openwrt-devel
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, I'm working on porting a seco

[OpenWrt-Devel] [PATCH] ath79: do not set inherited phy-mode/status properties again

2020-01-27 Thread Adrian Schmutzler
There are several cases where phy-mode and status properties are set again in DTS(I) files although those were set to the same values in parent DTSI files already. Remove those cases (and thus also stop their proliferation by copy/paste). Signed-off-by: Adrian Schmutzler --- target/linux/ath79/d

Re: [OpenWrt-Devel] 19.07.0 boot hang on Mikrotik device

2020-01-27 Thread Joe Ayers
> > > > You should report this bug under "openwrt-19.07": > > https://bugs.openwrt.org/ > > > > You are apparently using ar71xx, did you try an ath79 19.07 image? > > the first mikrotik device in ath79 was merged to master last week, so ath79 > is not an option here ATM. > > Best > > Adrian > > >

Re: [OpenWrt-Devel] 19.07.0 boot hang on Mikrotik device

2020-01-27 Thread Koen Vandeputte
On 27.01.20 17:14, Joe Ayers wrote: You should report this bug under "openwrt-19.07": https://bugs.openwrt.org/ You are apparently using ar71xx, did you try an ath79 19.07 image? the first mikrotik device in ath79 was merged to master last week, so ath79 is not an option here ATM. Best Adr

Re: [OpenWrt-Devel] ath79: NAND bad eraseblocks in MikroTik RouterBOARD 922UAGS-5HPacD

2020-01-27 Thread Koen Vandeputte
Hi Roger, Can you send me full bootlogs please from both? I have RB922-5HPnD, not the AC version over here, but I guess the issue will also be present over there. Thanks again, Koen On 27.01.20 15:16, Roger Pueyo Centelles | Guifi.net via openwrt-devel wrote: The sender domain has a DMARC

Re: [OpenWrt-Devel] ath79: NAND bad eraseblocks in MikroTik RouterBOARD 922UAGS-5HPacD

2020-01-27 Thread Roger Pueyo Centelles | Guifi.net via openwrt-devel
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 Koen, Please find the bootlogs

[OpenWrt-Devel] [RFC PATCH] ath9k: enable hardware random number generator.

2020-01-27 Thread Rui Salvaterra
The ath9k driver is able to leverage the PHY ADC in order to provide a generic hardware random number generator to the kernel, filling up the entropy pool as required. Expose this feature in the build system and remove the old entropy patch, which only obtains entropy from the ADC once, when the at

Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet

2020-01-27 Thread Piotr Dymacz
Hi Adrian, On 21.01.2020 15:10, Adrian Schmutzler wrote: [...] I'm in the middle of migrating some devices from soon-to-be-obsolete ar71xx to ath79 target and was wondering about status of the eth0/eth1 vs. LAN/WAN assignment issue. To start with the end: I've decided to stop working on this

Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet

2020-01-27 Thread Adrian Schmutzler
Just a quick one: > > So, no matter what we do, there is no easy way forward. > > We could remove all ar71xx -> ath79 migration helper scripts, ar71xx > board names from supported devices lists in ath79 images and make the > target a brand new, without any concerns about soon-to-be obsolete ar71x

Re: [OpenWrt-Devel] [PATCH 18.06] libubox: backport security patches

2020-01-27 Thread Hauke Mehrtens
On 1/26/20 4:55 PM, Hauke Mehrtens wrote: > This backports some security relevant patches from libubox master. These > patches should not change the existing API and ABI so that old > applications still work like before without any recompilation. > Application can not also use more secure APIs. >

Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet

2020-01-27 Thread Peter Geis
On Mon, Jan 27, 2020 at 1:35 PM Adrian Schmutzler wrote: > > Just a quick one: > > > > So, no matter what we do, there is no easy way forward. > > > > We could remove all ar71xx -> ath79 migration helper scripts, ar71xx > > board names from supported devices lists in ath79 images and make the > >

Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet

2020-01-27 Thread Piotr Dymacz
Hi Adrian, On 27.01.2020 19:35, Adrian Schmutzler wrote: Just a quick one: > So, no matter what we do, there is no easy way forward. We could remove all ar71xx -> ath79 migration helper scripts, ar71xx board names from supported devices lists in ath79 images and make the target a brand new, w

Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet

2020-01-27 Thread Piotr Dymacz
Hi Peter, On 27.01.2020 19:57, Peter Geis wrote: On Mon, Jan 27, 2020 at 1:35 PM Adrian Schmutzler wrote: Just a quick one: > > So, no matter what we do, there is no easy way forward. > > We could remove all ar71xx -> ath79 migration helper scripts, ar71xx > board names from supported device

Re: [OpenWrt-Devel] Migration in ath79 for swapped ethernet

2020-01-27 Thread Peter Geis
On Mon, Jan 27, 2020 at 4:00 PM Piotr Dymacz wrote: > > Hi Peter, > > On 27.01.2020 19:57, Peter Geis wrote: > > On Mon, Jan 27, 2020 at 1:35 PM Adrian Schmutzler > > wrote: > >> > >> Just a quick one: > >> > >> > > So, no matter what we do, there is no easy way forward. > >> > > >> > We could re