Re: [OpenWrt-Devel] [PATCH-19.07] build: fix module strip invalid

2019-10-30 Thread 大雄
Build file drivers/net/ethernet/intel/e1000e/e1000e.ko size about 920KB for old PATCH. After the new patch is about 177KB From: Hauke Mehrtens Date: 2019-10-30 23:47 To: daxiong; openwrt-devel Subject: Re: [OpenWrt-Devel] [PATCH-19.07] build: fix module strip invalid On 10/30/19 11:14 AM,

Re: [OpenWrt-Devel] [PATCH] hostapd: enable PMKSA and OK caching for WPA3-Personal

2019-10-30 Thread David Bauer
Hello Hauke, On 10/30/19 8:47 PM, Hauke Mehrtens wrote: > Do you know which, PMKSA or OKC, is needed for the iPhone? PMKSA caching is the one required to work with the iPhone (however OKC should not be harmful). > > I do not understand why the iPhone only works when one of these options > is

Re: [OpenWrt-Devel] [PATCH netifd 2/5] wireless: serialize wireless interface configuration

2019-10-30 Thread John Crispin
On 30/10/2019 16:56, Daniel Golle wrote: + wdev->serialize = true; this should default to false, my bad, it's a leftover from my testing setup, will fixup when I merge the patch John ___ openwrt-devel mailing list

Re: [OpenWrt-Devel] v5.4 as next kernel

2019-10-30 Thread Stefan Lippers-Hollmann
Hi On 2019-10-30, Adrian Schmutzler wrote: > 1. We currently have work-in-progress 4.19 support PRs for ramips, > ipq806x and bcm63xx, still with considerable work to do at least for > the first two (IIRC). Kernel 4.19 has been working fine on ipq806x (nbg6817) for me so far, I've been using it

Re: [OpenWrt-Devel] [PATCH] hostapd: enable PMKSA and OK caching for WPA3-Personal

2019-10-30 Thread Hauke Mehrtens
On 10/29/19 11:42 PM, David Bauer wrote: > This enables PMKSA and opportunistic key caching by default for > WPA2/WPA3-Personal, WPA3-Personal and OWE auth types. > Otherwise, Apple devices won't connect to the WPA3 network. > > This should not degrade security, as there's no external

Re: [OpenWrt-Devel] v5.4 as next kernel

2019-10-30 Thread Hauke Mehrtens
On 10/30/19 6:25 PM, Piotr Dymacz wrote: > Hi Hauke, John, > > On 30.10.2019 16:54, Hauke Mehrtens wrote: >> On 10/29/19 6:37 AM, John Crispin wrote: >>> Hi, >>> should we use v5.4 as our next kernel ? >>> John >> >> I also agree to have kernel 5.4 as the next kernel, it will be finally >>

[OpenWrt-Devel] [PATCH] ipq40xx: convert IMAGE_SIZE/KERNEL_SIZE/BLOCKSIZE to kiB

2019-10-30 Thread Adrian Schmutzler
This cosmetical patch converts IMAGE_SIZE, KERNEL_SIZE and BLOCKSIZE definitions to kilobytes, as this is consistent and easier to read/type. An exception was made for asus_rt-ac58u, where the IMAGE_SIZE of 20439364 cannot be divided by 1024 (and also does not seem to match anything in DTS).

Re: [OpenWrt-Devel] v5.4 as next kernel

2019-10-30 Thread Jeff Kletsky
On 10/30/19 9:50 AM, Hauke Mehrtens wrote: On 10/30/19 5:29 PM, Adrian Schmutzler wrote: Hi, -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Hauke Mehrtens Sent: Mittwoch, 30. Oktober 2019 16:54 To: John Crispin ; OpenWrt

Re: [OpenWrt-Devel] v5.4 as next kernel

2019-10-30 Thread Piotr Dymacz
Hi Hauke, John, On 30.10.2019 16:54, Hauke Mehrtens wrote: On 10/29/19 6:37 AM, John Crispin wrote: Hi, should we use v5.4 as our next kernel ? John I also agree to have kernel 5.4 as the next kernel, it will be finally released in about 1 months and it is a long term kernel. If we are

Re: [OpenWrt-Devel] v5.4 as next kernel

2019-10-30 Thread Hauke Mehrtens
On 10/30/19 5:29 PM, Adrian Schmutzler wrote: > Hi, > >> -Original Message- >> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On >> Behalf Of Hauke Mehrtens >> Sent: Mittwoch, 30. Oktober 2019 16:54 >> To: John Crispin ; OpenWrt Development List >> >> Subject: Re:

Re: [OpenWrt-Devel] v5.4 as next kernel

2019-10-30 Thread Adrian Schmutzler
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On > Behalf Of Hauke Mehrtens > Sent: Mittwoch, 30. Oktober 2019 16:54 > To: John Crispin ; OpenWrt Development List > > Subject: Re: [OpenWrt-Devel] v5.4 as next kernel > > On 10/29/19

Re: [OpenWrt-Devel] [PATCH 3/3] ipq40xx: ipq4019: Add new device Compex WPJ419

2019-10-30 Thread Adrian Schmutzler
Hi, > > + m25p80@0 { > > + #address-cells = <1>; > > + #size-cells = <1>; > > + reg = <0>; > > + linux,modalias = "m25p80", "n25q128a11"; > > +

[OpenWrt-Devel] [PATCH 4/5] mac80211: add support for dynamically reconfiguring wifi

2019-10-30 Thread Daniel Golle
From: John Crispin Change scripts to use ubus interface of hostapd/wpa_supplicant to add/remove/modify wireless interfaces instead of (re-)starting the services. Signed-off-by: Daniel Golle --- .../files/lib/netifd/wireless/mac80211.sh | 135 ++ 1 file changed, 107

[OpenWrt-Devel] [PATCH netifd 2/5] wireless: serialize wireless interface configuration

2019-10-30 Thread Daniel Golle
From: John Crispin Signed-off-by: Daniel Golle --- wireless.c | 57 -- wireless.h | 7 +++ 2 files changed, 62 insertions(+), 2 deletions(-) diff --git a/wireless.c b/wireless.c index 9986e9a..06afea3 100644 --- a/wireless.c +++

[OpenWrt-Devel] [PATCH 5/5] base-files: add 'wifi reconf'

2019-10-30 Thread Daniel Golle
From: John Crispin Now that netifd and hostapd allow dynamic reconfiguration, add a command to trigger it. Signed-off-by: Daniel Golle --- package/base-files/files/sbin/wifi | 5 + 1 file changed, 5 insertions(+) diff --git a/package/base-files/files/sbin/wifi

[OpenWrt-Devel] [PATCH 3/5] hostapd: add ubus reload

2019-10-30 Thread Daniel Golle
From: John Crispin Add ubus interface to hostapd and wpa_supplicant to allow dynamically reloading wiface configuration without having to restart the hostapd process. As a consequence, bost hostapd and wpa_supplicant are now started persistently on boot for each wifi device in the system and

Re: [OpenWrt-Devel] ath79/qca9533rev2: Help needed on missing GPIO on ath9k-phy0

2019-10-30 Thread Piotr Dymacz
Hi Adrian, On 30.10.2019 15:30, Adrian Schmutzler wrote: Hi, we are still working on broken WiFi on CPE210v2/v3 (ath79, QCA9533 rev. 2) and have found that on ath79 a GPIO is missing compared to ar71xx (where WIFI is working): It's not missing, it's there, just not controlled by the ath9k

[OpenWrt-Devel] [PATCH netifd 1/5] wireless: add ubus method for reloading configuration

2019-10-30 Thread Daniel Golle
From: John Crispin Signed-off-by: Daniel Golle --- ubus.c | 23 +++ wireless.c | 18 +- wireless.h | 1 + 3 files changed, 37 insertions(+), 5 deletions(-) diff --git a/ubus.c b/ubus.c index 150d818..5a2a339 100644 --- a/ubus.c +++ b/ubus.c @@ -1081,6

Re: [OpenWrt-Devel] [PATCH-19.07] build: fix module strip invalid

2019-10-30 Thread Hauke Mehrtens
On 10/30/19 11:14 AM, daxiong wrote: > Current modpost cannot reduce the module size. > > Use $(STRIP) command to replace the modpost patch, > I think to be compatibility will be better. > > Signed-off-by: daxiong Please base this against master, then we can backport it to 19.07. Could you

Re: [OpenWrt-Devel] v5.4 as next kernel

2019-10-30 Thread Hauke Mehrtens
On 10/29/19 6:37 AM, John Crispin wrote: > Hi, > should we use v5.4 as our next kernel ? > John I also agree to have kernel 5.4 as the next kernel, it will be finally released in about 1 months and it is a long term kernel. If we are lucky it will be supported for 6 years for Android. What

Re: [OpenWrt-Devel] [PATCH 3/3] ipq40xx: ipq4019: Add new device Compex WPJ419

2019-10-30 Thread Jeff Kletsky
On 10/30/19 4:27 AM, Daniel Danzberger wrote: This device contains 2 flash devices. One NOR (32M) and one NAND (128M). U-boot and caldata are on the NOR, the firmware on the NAND. SoC:IPQ4019 CPU:4x 710MHz ARMv7 RAM:256MB FLASH: NOR:32MB NAND:128MB [...]

Re: [OpenWrt-Devel] [PATCH 0/6] buildsystem: Activate PIE ASLR for some packages

2019-10-30 Thread Hauke Mehrtens
On 10/28/19 10:14 AM, Daniel Engberg wrote: > On 2019-10-27 18:44, Hauke Mehrtens wrote: >> This is a follow up patch on this discussion on the mailing list: >> https://patchwork.ozlabs.org/patch/1041647/ >> >> This allows to activate PIE only for some packages where we thing it is >> necessary

Re: [OpenWrt-Devel] ath79/qca9533rev2: Help needed on missing GPIO on ath9k-phy0

2019-10-30 Thread Tom Psyborg
What about ar9533 devices on ath79 that do have working wifi, is that gpio present there? As far as I understand the idea was to use alias gpio chip (starting from 494) on ath79 instead of generic gpio (0-31) but I might be wrong about this. ___

Re: [OpenWrt-Devel] [PATCH 1/3] ipq40xx: Add gigadevice nandspi flash driver

2019-10-30 Thread Daniel Danzberger
> Is there a reason why the upstream SPI-NAND framework isn't being used? No, I didn't know about it. The patches I used are copied from a compex openwrt tree and have only been modified by me to run on kernel 4.19 I am going to checkout the new API and try to make the device work with it. On

Re: [OpenWrt-Devel] [PATCH 1/3] ipq40xx: Add gigadevice nandspi flash driver

2019-10-30 Thread Jeff Kletsky
On 10/30/19 4:27 AM, Daniel Danzberger wrote: This patch adds support for Gigadevice SPI NAND device to the mt29f stagging driver. Signed-off-by: Daniel Danzberger --- ...port-gigadevice-nandspi-flash-device.patch | 1778 + 1 file changed, 1778 insertions(+) create mode

Re: [OpenWrt-Devel] ath79/qca9533rev2: Help needed on missing GPIO on ath9k-phy0

2019-10-30 Thread Adrian Schmutzler
Hi Dmitry, > Where I can see the DTS? Generally ath9k gpio is added by > gpio-controller property to the ath9k node. See dir825b1 as an example > an many others. ath79: https://github.com/openwrt/openwrt/blob/master/target/linux/ath79/dts/qca9533_tplink_cpe210.dtsi

Re: [OpenWrt-Devel] ath79/qca9533rev2: Help needed on missing GPIO on ath9k-phy0

2019-10-30 Thread Dmitry Tunin
Is one wireless adapter connected using PCIE? If it is true, you'll have to set it's node in DTS. Generally it's not required, but if you need a gpio controller, then you have to. ср, 30 окт. 2019 г. в 17:51, Dmitry Tunin : > > ср, 30 окт. 2019 г. в 17:31, Adrian Schmutzler : > > > > Hi, > > > >

Re: [OpenWrt-Devel] ath79/qca9533rev2: Help needed on missing GPIO on ath9k-phy0

2019-10-30 Thread Dmitry Tunin
ср, 30 окт. 2019 г. в 17:31, Adrian Schmutzler : > > Hi, > > we are still working on broken WiFi on CPE210v2/v3 (ath79, QCA9533 rev. 2) > and have found that on ath79 a GPIO is missing compared to ar71xx (where WIFI > is working): > > GPIO Config on the ar71xx: > > gpiochip0: GPIOs 0-31, parent:

Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for Netgear WNDR4300

2019-10-30 Thread Adrian Schmutzler
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On > Behalf Of Michal Cieslakiewicz > Sent: Mittwoch, 30. Oktober 2019 15:28 > To: Adrian Schmutzler > Cc: openwrt-devel@lists.openwrt.org > Subject: Re: [OpenWrt-Devel] [PATCH v2] ath79: add

[OpenWrt-Devel] ath79/qca9533rev2: Help needed on missing GPIO on ath9k-phy0

2019-10-30 Thread Adrian Schmutzler
Hi, we are still working on broken WiFi on CPE210v2/v3 (ath79, QCA9533 rev. 2) and have found that on ath79 a GPIO is missing compared to ar71xx (where WIFI is working): GPIO Config on the ar71xx: gpiochip0: GPIOs 0-31, parent: platform/ath79-gpio, ath79-gpio: gpio-11 (

Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for Netgear WNDR4300

2019-10-30 Thread Michal Cieslakiewicz
Hello Adrian, Thanks for your feedback! > Hi, > > Same question I asked on zyxel support: Do you expect several further > netgear devices to be added to nand target? > > Up to let's say three/four devices, I'd prefer to merge stuff into > nand.mk, otherwise I'd say a separate file is

Re: [OpenWrt-Devel] [PATCH 2/3] ipq40xx: mtd m25p80: fix hang on device shutdown

2019-10-30 Thread Piotr Dymacz
Hi Daniel, On 30.10.2019 12:27, Daniel Danzberger wrote: Signed-off-by: Daniel Danzberger --- .../401-mtd-m25p80-fix-shutdown-hang.patch| 21 +++ 1 file changed, 21 insertions(+) create mode 100644

Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for Netgear WNDR4300

2019-10-30 Thread Adrian Schmutzler
Hi, > diff --git a/target/linux/ath79/image/Makefile > b/target/linux/ath79/image/Makefile > index 24768ef5e0..b6ac83cdc1 100644 > --- a/target/linux/ath79/image/Makefile > +++ b/target/linux/ath79/image/Makefile > @@ -77,6 +77,7 @@ include ./generic-ubnt.mk > endif > ifeq ($(SUBTARGET),nand)

Re: [OpenWrt-Devel] [PATCH 3/3] ipq40xx: ipq4019: Add new device Compex WPJ419

2019-10-30 Thread Adrian Schmutzler
Hi, just some cosmetical drive-by comments below: ... > diff --git > a/target/linux/ipq40xx/base-files/etc/hotplug.d/firmware/11-ath10k-caldata > b/target/linux/ipq40xx/base- > files/etc/hotplug.d/firmware/11-ath10k-caldata > index 2336ef3c7b..b18d17e422 100644 > ---

[OpenWrt-Devel] [PATCH v2] ath79: add support for Netgear WNR2200

2019-10-30 Thread Michal Cieslakiewicz
This patch adds ath79 support for Netgear WNR2200. Router was previously supported by ar71xx target only (8 MiB variant). Netgear WNR2200 has two flash versions - 8MiB sold in EU, US etc. and 16 MiB for Russia and China markets. Apart from flash size both variants share the same hardware

[OpenWrt-Devel] [PATCH v2] ath79: add support for Netgear WNDR4300

2019-10-30 Thread Michal Cieslakiewicz
This patch adds ath79 support for Netgear WNDR4300. Router was previously supported by ar71xx target only. Note: device requires 'ar934x-nand' driver in kernel. Specification = * Description: Netgear WNDR4300 * Loader: U-boot * SOC: Atheros AR9344 (560 MHz) * RAM: 128 MiB *

Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for Netgear WNR2200

2019-10-30 Thread Michal Cieslakiewicz
Hello, This patch supersedes previous version (also listed on patchwork: https://patchwork.ozlabs.org/patch/1181348/) and implements following changes: * scripts have been rebased to apply after base-files split * router added to uboot-envtools * device name in image header changed to lowercase

Re: [OpenWrt-Devel] [PATCH v2] ath79: add support for Netgear WNDR4300

2019-10-30 Thread Michal Cieslakiewicz
Hello, This patch supersedes WNR4300 patchset: https://patchwork.ozlabs.org/patch/1175066/ (obsolete - removed) https://patchwork.ozlabs.org/patch/1175069/ (updated to v2) It contains changes proposed by Adrian (remove redundant lan_mac setting from 02_network; change MAC label to eth0

Re: [OpenWrt-Devel] [PATCH 1/3] ipq40xx: Add gigadevice nandspi flash driver

2019-10-30 Thread Robert Marko
On Wed, 30 Oct 2019 at 12:28, Daniel Danzberger wrote: > > This patch adds support for Gigadevice SPI NAND device to the mt29f stagging > driver. Which model of SPI NAND does this board use? MT29F was removed in 4.21 and should not be used as upstream SPI-NAND framework replaced it in vendor

[OpenWrt-Devel] [PATCH 1/3] ipq40xx: Add gigadevice nandspi flash driver

2019-10-30 Thread Daniel Danzberger
This patch adds support for Gigadevice SPI NAND device to the mt29f stagging driver. Signed-off-by: Daniel Danzberger --- ...port-gigadevice-nandspi-flash-device.patch | 1778 + 1 file changed, 1778 insertions(+) create mode 100644

[OpenWrt-Devel] [PATCH 0/3] ipq40xx: Add new device Compex WPJ419

2019-10-30 Thread Daniel Danzberger
These 3 patches add support for the Compex WPJ419 board. Patch 1 adds the nandspi driver for the Gigadevice flash used on the wpj419. Patch 2 fixes a reboot/shutdown hang. Patch 3 Adds the actual wpj419 device support. ___ openwrt-devel mailing list

[OpenWrt-Devel] [PATCH 2/3] ipq40xx: mtd m25p80: fix hang on device shutdown

2019-10-30 Thread Daniel Danzberger
Signed-off-by: Daniel Danzberger --- .../401-mtd-m25p80-fix-shutdown-hang.patch| 21 +++ 1 file changed, 21 insertions(+) create mode 100644 target/linux/ipq40xx/patches-4.19/401-mtd-m25p80-fix-shutdown-hang.patch diff --git

[OpenWrt-Devel] [PATCH 3/3] ipq40xx: ipq4019: Add new device Compex WPJ419

2019-10-30 Thread Daniel Danzberger
This device contains 2 flash devices. One NOR (32M) and one NAND (128M). U-boot and caldata are on the NOR, the firmware on the NAND. SoC:IPQ4019 CPU:4x 710MHz ARMv7 RAM:256MB FLASH: NOR:32MB NAND:128MB ETH:2x GMAC Gigabit POE:802.3 af/at POE,

Re: [OpenWrt-Devel] improved handling of contributions [Was: Re: patches from 2018]

2019-10-30 Thread Petr Štetiar
Adrian Schmutzler [2019-10-29 13:25:27]: Hi, > the main difference is just that I prefer some manual interference, where > you are looking for more automation: 1. DRY 2. Avoiding manual mistakes (and introduce automated ones) 3. Time spent on the tasks which could be automated could be used in

[OpenWrt-Devel] [PATCH-19.07] build: fix module strip invalid

2019-10-30 Thread daxiong
Current modpost cannot reduce the module size. Use $(STRIP) command to replace the modpost patch, I think to be compatibility will be better. Signed-off-by: daxiong --- .../linux/generic/hack-4.14/204-module_strip.patch | 216 +++-- 1 file changed, 24 insertions(+), 192

[OpenWrt-Devel] [PATCH-19.07] build: fix module strip invalid

2019-10-30 Thread daxiong
Current modpost cannot reduce the module size. Use $(STRIP) command to replace the modpost patch, I think to be compatibility will be better. Signed-off-by: daxiong --- .../linux/generic/hack-4.14/204-module_strip.patch | 220 +++-- 1 file changed, 28 insertions(+), 192