Re: [OpenWrt-Devel] [PATCH] wireless-regdb: fix build when python2 from package feeds exists

2019-07-31 Thread Lucian Cristian
On 31.07.2019 23:31, Petr Štetiar wrote: wireless-regdb fails to build if there is python2 installed from package feeds, as staging_dir/hostpkg/bin/python is python2 and staging_dir/hostpkg/bin takes precedence over staging_dir/host/bin (proper place with python -> python3 symlink) which leads to

[OpenWrt-Devel] [PATCH] mxs: add support and switch to kernel 4.19

2019-07-31 Thread Michael Heimpold
Also remove kernel 4.14 support and the meanwhile obsolete patch. This was run-tested on I2SE Duckbill device and Olimex OLinuXino Maxi board. Signed-off-by: Michael Heimpold --- target/linux/mxs/Makefile | 2 +- target/linux/mxs/{config-4.14 => config-4.19} | 42 +++---

[OpenWrt-Devel] [PATCH] uboot-mxs: bump to v2019.07

2019-07-31 Thread Michael Heimpold
Also update the U-Boot BSP patch for I2SE Duckbill devices. Run tested on I2SE Duckbill and Olimex OLinuXino Maxi boards. Signed-off-by: Michael Heimpold --- package/boot/uboot-mxs/Makefile | 4 ++-- .../uboot-mxs/patches/001-add-i2se-duckbill.patch | 13 +++-- 2

[OpenWrt-Devel] [PATCH] uboot-mxs: bump to v2019.07

2019-07-31 Thread Michael Heimpold
Also update the U-Boot BSP patch for I2SE Duckbill devices. Run tested on I2SE Duckbill and Olimex OLinuXino Maxi boards. Signed-off-by: Michael Heimpold --- package/boot/uboot-mxs/Makefile | 4 ++-- .../uboot-mxs/patches/001-add-i2se-duckbill.patch | 13 +++-- 2

[OpenWrt-Devel] [PATCH] wireless-regdb: fix build when python2 from package feeds exists

2019-07-31 Thread Petr Štetiar
wireless-regdb fails to build if there is python2 installed from package feeds, as staging_dir/hostpkg/bin/python is python2 and staging_dir/hostpkg/bin takes precedence over staging_dir/host/bin (proper place with python -> python3 symlink) which leads to the build failure of wireless-regdb, so th

[OpenWrt-Devel] Memory leak related to OpenWrt patch of hostapd

2019-07-31 Thread Nick Schaf
Hello, I've noticed the wpa_supplicant process on my mesh interfaces leaking memory to the point that the kernel kills the process. It was discovered in 18.06.2, but I've reproduced it with 18.06.4 and with the master branch from the GitHub repo. Since the leak occurs as mesh links are created

[OpenWrt-Devel] GitHub starts blocking developers in countries facing US trade sanctions

2019-07-31 Thread Paul Oranje
LWN posted an article with the above title [1] that refers itself to an article on ZDNet [2]. [1] https://lwn.net/Articles/794752/ [2] https://www.zdnet.com/article/github-starts-blocking-developers-in-countries-facing-us-trade-sanctions/ ___ openwr

[OpenWrt-Devel] RE??RE: RE??RE: [PATCH] ramips: add support to JS7628 development board

2019-07-31 Thread Robinson Wu
Hi Adrian, It is ok to rename my devices without memory size. I will add two types of board which are named "JS7688"(MT7688AN chip) and "ZTK7628P"(MT7628DAN chip), after "JS7628" commit succeed . These boards are based on "*js76x8.dtsi" as they all have the same chip core. Best Robinson wu