[OpenWrt-Devel] [PATCH 1/4] mvebu: add Turris Omnia LED support

2018-12-12 Thread Klaus Kudielka
The kernel driver is directly pulled from TurrisOS. https://gitlab.labs.nic.cz/turris/turris-build/commit/60f75b6b I have added the associated extension of the device tree. Signed-off-by: Klaus Kudielka --- .../mvebu/patches-4.14/490-omnia-leds.patch | 568 ++ 1 file changed,

[OpenWrt-Devel] [PATCH 4/4] mvebu: add Turris Omnia LED configuration

2018-12-12 Thread Klaus Kudielka
With this commit users are able to configure all extra features of the Turris Omnia LED driver (global brightness, individual LED color, individual autonomous flag). For example: uci set omnia_led.main.global_brightness='6' uci set omnia_led.power.color='255 0 0' service omnia_led start uci

[OpenWrt-Devel] [PATCH 2/4] mvebu: enable Turris Omnia LED support as module

2018-12-12 Thread Klaus Kudielka
leds.mk: - Define kmod-leds-omnia including dependencies. - Load early, in order to support LED diagnostics during preinit. cortex-a9.mk: - Select kmod-leds-omnia for the turris-omnia image. i2c.mk: - LED controller is behind i2c mux. Therefore, load i2c-mux-pca954x early as well.

[OpenWrt-Devel] [PATCH 0/4] mvebu: add Turris Omnia LED support

2018-12-12 Thread Klaus Kudielka
This patchset adds LED support for the Turris Omnia, enables LED diagnostics, and adds UCI configuration capability for the non-standard features of the driver (color, autonomous, global_brightness). Tested on my Turris Omnia. Klaus Kudielka (4): mvebu: add Turris Omnia LED support mvebu:

[OpenWrt-Devel] [PATCH 3/4] mvebu: enable LED diagnostics for Turris Omnia

2018-12-12 Thread Klaus Kudielka
Just before starting LED diagnostics, a preinit hook disables the 'autonomous' flag for all LEDs. This way, the power LED will start blinking during preinit, as desired. As a benefit, all other LEDs remain dark, until boot is finished (and the desired LED configuration is loaded). This avoids the

Re: [OpenWrt-Devel] [PATCH 0/5] ath79: Add support for Ubiquiti Nanostation M (XW)

2018-12-12 Thread Petr Štetiar
FYI, I've moved with version v2 of this patch series to GitHub[1]. 1. https://github.com/openwrt/openwrt/pull/1632 -- ynezz ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] hostapd 2.7 released

2018-12-12 Thread Michael Marley
On 2018-12-12 14:37, Hauke Mehrtens wrote: On 12/12/18 10:39 AM, Daniel Golle wrote: Hi! hostapd 2.7 has been released on December 2nd: http://w1.fi/cgit/hostap/plain/hostapd/ChangeLog I've updated the hostapd package to use the hostapd_2_7 tag with our patches on top, find it in my staging

[OpenWrt-Devel] [PATCH v2] ath10k-ct: Update to 2018-12-11 and use version based on 4.19

2018-12-12 Thread Hauke Mehrtens
This updates the ath10k-ct driver to the version from 2018-12-11 and selects the ath10k-ct version based on kernel 4.19 by default. CONFIG_ATH10K_CE was introduced between kernel 4.16 and 4.19 and is a mandatory option. Signed-off-by: Hauke Mehrtens --- changes since v1: * Add description *

Re: [OpenWrt-Devel] brcm2708: add kernel 4.14 support

2018-12-12 Thread Stijn Tintel
On 7/12/18 05:06, Stijn Tintel wrote: > On 11/11/18 18:37, Stijn Tintel wrote: >> Hi, >> >> I have just pushed support for the 4.14 kernel on the brcm2708 target to >> my staging tree [1], and would like to get some feedback before pushing >> it to master. It would also be nice if people could do

Re: [OpenWrt-Devel] hostapd 2.7 released

2018-12-12 Thread Hauke Mehrtens
On 12/12/18 10:39 AM, Daniel Golle wrote: > Hi! > > hostapd 2.7 has been released on December 2nd: > http://w1.fi/cgit/hostap/plain/hostapd/ChangeLog > > I've updated the hostapd package to use the hostapd_2_7 tag with our > patches on top, find it in my staging tree: >

[OpenWrt-Devel] [PATCH] ath10k-firmware: update all CT firmware variants

2018-12-12 Thread Michael Yartys
Wave-1 firmware (988x, 9887): bug fixes Wave-2 firmware (4019, 9888, 99x0, 9984): fix protected management frames, rate-ctrl fixes, and performance improvements Signed-off-by: Michael Yartys --- package/firmware/ath10k-firmware/Makefile | 64 +++ 1 file changed, 32

[OpenWrt-Devel] [PATCH v3] ath79: add support for TP-Link Archer A7

2018-12-12 Thread Karl-Felix Glatzer
This patch adds support for TP-Link Archer A7 Specification: - SOC: QCA9563 - Flash: 16 MiB (SPI) - RAM: 128 MiB (DDR2) - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: - 2.4GHz (bgn) SoC internal - 5GHz (ac) QCA988x - USB: 1x USB 2.0 port - Button: 1x power, 1x reset, 1x wps - LED: 10x

Re: [OpenWrt-Devel] Changes in support for Mikrotik RB493G

2018-12-12 Thread Mathias Kresin
09/12/2018 21:44, W. Michael Petullo: Changes in the last year or so have left me a little confused with the OpenWrt support for the Mikrotik RB493G. I generally compile my kernels and root disk images myself, namely by running "make menuconfig" and "make" in an OpenWrt source tree. I then go on

[OpenWrt-Devel] [PATCH 1/2] blockd: unmount device explicitly when it disappears

2018-12-12 Thread Rafał Miłecki
From: Rafał Miłecki To keep autofs behavior consistent blockd should request both: mounting and unmounting when needed. It's important as autofs-related actions may require slightly different handling. Without this patch: 1) autofs mounts were handled using TYPE_AUTOFS 2) autofs unmounts were

[OpenWrt-Devel] [PATCH 2/2] block(d): improve hotplug.d "mount" events for the autofs

2018-12-12 Thread Rafał Miłecki
From: Rafał Miłecki So far - when using autofs - "add" and "remove" action events were triggered on every (un)mount. It wasn't very helpful when using autofs due to its nature. The point of blockd & autofs is to have block devices mounted on an access request. Its users should not care / know

Re: [OpenWrt-Devel] [PATCH 5/5] ath79: Add support for Ubiquiti Nanostation M (XW)

2018-12-12 Thread Petr Štetiar
Mathias Kresin [2018-12-12 13:40:40]: Hi, > > + { > > + status = "okay"; > > + > > + phy-mode = "mii"; > > + phy-handle = <>; > > + mtd-mac-address = < 0x0>; > > Can't the mtd-mac-address be moved to the ar9342_ubnt_xw.dtsi? yes, I'll do it. > Don't we need pll-data here? Well, I

Re: [OpenWrt-Devel] [PATCH 2/5] ath79: ubnt-bullet-m-xw: Move common DTS bits into XW include file

2018-12-12 Thread Petr Štetiar
Mathias Kresin [2018-12-12 13:27:17]: Hi Mathias, > > phy-mask = <4>; > > + > > phy4: ethernet-phy@4 { > > - phy-mode = "rgmii"; > > reg = <4>; > > + phy-mode = "rgmii"; > > }; > > }; > > Unrelated noop change. Please drop it. Ok. > >{ > >

Re: [OpenWrt-Devel] [PATCH 1/5] ath79: ubnt-xw: Add LED aliases for diag and status LED support

2018-12-12 Thread Mathias Kresin
12/12/2018 13:46, Petr Štetiar: Mathias Kresin [2018-12-12 13:22:08]: --- a/target/linux/ath79/dts/ar9342_ubnt_xw.dtsi +++ b/target/linux/ath79/dts/ar9342_ubnt_xw.dtsi @@ -9,15 +9,22 @@ compatible = "ubnt,xw", "qca,ar9342"; model = "Ubiquiti Networks XW board"; + aliases

Re: [OpenWrt-Devel] [PATCH 1/5] ath79: ubnt-xw: Add LED aliases for diag and status LED support

2018-12-12 Thread Petr Štetiar
Mathias Kresin [2018-12-12 13:22:08]: > > --- a/target/linux/ath79/dts/ar9342_ubnt_xw.dtsi > > +++ b/target/linux/ath79/dts/ar9342_ubnt_xw.dtsi > > @@ -9,15 +9,22 @@ > > compatible = "ubnt,xw", "qca,ar9342"; > > model = "Ubiquiti Networks XW board"; > > + aliases { > > +

Re: [OpenWrt-Devel] [PATCH 5/5] ath79: Add support for Ubiquiti Nanostation M (XW)

2018-12-12 Thread Mathias Kresin
Hey Petr, more comments inline. Mathias 10/12/2018 23:46, Petr Štetiar: CPU: AR9342 SoC RAM: 64 MB DDR2 Flash: 8 MB NOR SPI Ports: 2x100 MBit (24V PoE in, 24V PoE out), AR8236 switch WLAN: 2.4/5 GHz UART: 1 UART LEDs:Power, 2x Ethernet, 4x RSSI LEDs (orange, red, 2x

Re: [OpenWrt-Devel] [PATCH 3/5] ath79: gmac: ar934x: Add parser for mii-gmac0-slave

2018-12-12 Thread Mathias Kresin
10/12/2018 23:46, Petr Štetiar: In ar71xx/mach-ubnt-xm.c there's following code: static void __init ubnt_xw_init(void) { ... ath79_setup_ar934x_eth_cfg(AR934X_ETH_CFG_MII_GMAC0 | AR934X_ETH_CFG_MII_GMAC0_SLAVE); ... } But I couldn't find a way how to set it up via DTS.

Re: [OpenWrt-Devel] [PATCH 2/5] ath79: ubnt-bullet-m-xw: Move common DTS bits into XW include file

2018-12-12 Thread Mathias Kresin
Hey Petr, find my comments inline. Mathias 10/12/2018 23:46, Petr Štetiar: Most of the M/XW platform settings can be shared so move those common DTS bits into include file. Tested-by: Joe Ayers Signed-off-by: Petr Štetiar --- target/linux/ath79/dts/ar9342_ubnt_bullet-m-xw.dts | 11

Re: [OpenWrt-Devel] [PATCH 1/5] ath79: ubnt-xw: Add LED aliases for diag and status LED support

2018-12-12 Thread Mathias Kresin
10/12/2018 23:46, Petr Štetiar: Currently there is no LED signalization for various system states implemented in diag.sh, so this patch adds support for it. Tested-by: Joe Ayers Signed-off-by: Petr Štetiar --- target/linux/ath79/dts/ar9342_ubnt_xw.dtsi | 13 ++--- 1 file changed,

[OpenWrt-Devel] hostapd 2.7 released

2018-12-12 Thread Daniel Golle
Hi! hostapd 2.7 has been released on December 2nd: http://w1.fi/cgit/hostap/plain/hostapd/ChangeLog I've updated the hostapd package to use the hostapd_2_7 tag with our patches on top, find it in my staging tree:

Re: [OpenWrt-Devel] 18.06-snapshots?

2018-12-12 Thread Jo-Philipp Wich
Hi, > Just wondering if there are snapshots built for the backports etc > done onto the 18.06 tree (e.g. in preparation for 18.06.2), or after > release are there only adhoc builds for release candidates for the > point release? http://downloads.openwrt.org/releases/18.06-SNAPSHOT/ > If there