[OpenWrt-Devel] [PATCH] ath79: add support for OCEDO Ursus

2019-03-19 Thread markus . scheck1
From: Markus Scheck SOC: Qualcomm Atheros QCA9558 RAM: 128MB FLASH: 16MB (Macronix MX25L12845EMI-10G) WLAN1: QCA9558 2.4GHz 802.11bgn 3SS WLAN2: QCA9880 5GHz 802.11ac 3SS LED: Power, LAN1, LAN2, 2.4GHz, 5GHz Serial:Next to SPI Flash, Pinout is 3V3 - GND - TX - RX (Square Pin is 3V3)

Re: [OpenWrt-Devel] qca8k: ipqess: ipq40xx: Kernel Panic on Adding VLAN Sub-Interface to Bridge

2019-03-19 Thread Jeff Kletsky
On 3/19/19 11:17 AM, Florian Fainelli wrote: On 3/19/19 11:14 AM, Christian Lamparter wrote: Cc: Florian. I hope you don't mind. On Tuesday, March 19, 2019 5:50:01 PM CET Jeff Kletsky wrote: Working with 4.19 / qca8k / ipqess patches from staging/chunkeey[1] on an IPQ4019-based device, I can

[OpenWrt-Devel] [PATCH] kernel: Backport ar933x_uart build fix (fixes FS#2152)

2019-03-19 Thread Petr Štetiar
Andrey has reported on OpenWrt's bug tracking system[1], that he currently can't use ar93xx_uart as pure serial UART without console (CONFIG_SERIAL_8250_CONSOLE and CONFIG_SERIAL_AR933X_CONSOLE undefined), because compilation ends with following error: ar933x_uart.c: In function 'ar933x_uart_cons

[OpenWrt-Devel] [PATCH] kernel: brcm47xx: Backport fixes for USB on WNDR3400v2 (fixes FS#2170)

2019-03-19 Thread Petr Štetiar
Eric has reported on OpenWrt's bug tracking system[1], that he's not able to use USB devices on his WNDR3400v2 device after the boot, until he turns on GPIO #21 manually through sysfs. 1. https://bugs.openwrt.org/index.php?do=details&task_id=2170 Signed-off-by: Petr Štetiar --- ...xx-Enable-USB

Re: [OpenWrt-Devel] [PATCH v2] iwinfo: Complete device IDs for Ubiquiti airOS XM/XW devices

2019-03-19 Thread Vincent Wiemann
Hi Mathias, I've put you in the CC as you have commit rights for the iwinfo repository. Regards, Vincent Wiemann (CodeFetch) On 16.03.2019 22:32, Vincent Wiemann wrote: > This commit includes all power offsets and subsystem device IDs > for Ubiquiti XM and XW devices. The device ID is wildcarde

Re: [OpenWrt-Devel] qca8k: ipqess: ipq40xx: Kernel Panic on Adding VLAN Sub-Interface to Bridge

2019-03-19 Thread Christian Lamparter
Cc: Florian. I hope you don't mind. On Tuesday, March 19, 2019 5:50:01 PM CET Jeff Kletsky wrote: > Working with 4.19 / qca8k / ipqess patches from staging/chunkeey[1] > on an IPQ4019-based device, I can get basic connectivity either manually, > or with a "standard" UCI definition of the "lan" bri

Re: [OpenWrt-Devel] qca8k: ipqess: ipq40xx: Kernel Panic on Adding VLAN Sub-Interface to Bridge

2019-03-19 Thread Florian Fainelli
On 3/19/19 11:14 AM, Christian Lamparter wrote: > Cc: Florian. I hope you don't mind. > > On Tuesday, March 19, 2019 5:50:01 PM CET Jeff Kletsky wrote: >> Working with 4.19 / qca8k / ipqess patches from staging/chunkeey[1] >> on an IPQ4019-based device, I can get basic connectivity either manually

Re: [OpenWrt-Devel] qca8k: ipqess: ipq40xx: Kernel Panic on Adding VLAN Sub-Interface to Bridge

2019-03-19 Thread Vincent Wiemann
Hi Jeff, sounds a bit like https://www.spinics.net/lists/netdev/msg552100.html Regards, Vincent Wiemann ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] qca8k: ipqess: ipq40xx: Kernel Panic on Adding VLAN Sub-Interface to Bridge

2019-03-19 Thread Jeff Kletsky
Working with 4.19 / qca8k / ipqess patches from staging/chunkeey[1] on an IPQ4019-based device, I can get basic connectivity either manually, or with a "standard" UCI definition of the "lan" bridge[2]. (I'm aware that this is not "production" code and expect "challenges".) However, I'm puzzled a

[OpenWrt-Devel] [PATCH] ath79: GL.iNet AR300M-nand/nor: correct LAN LED

2019-03-19 Thread Andreas Ziegler
The port labled as "LAN" is eth1. That's different from the -lite variant, where the only existing port eth0 is used as LAN Signed-off-by: Andreas Ziegler --- target/linux/ath79/base-files/etc/board.d/01_leds | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ath79/

Re: [OpenWrt-Devel] [PATCH] ath79: GL.iNet AR300M-nand/nor: correct LAN LED

2019-03-19 Thread Christian Lamparter
On Tuesday, March 19, 2019 12:59:16 AM CET Andreas Ziegler wrote: > The port labled as "LAN" is eth1. > That's different from the -lite variant, > where the only existing port eth0 is used as LAN Please resend your patch with a Signed-off-by. > --- > target/linux/ath79/base-files/etc/board.d/01_l

[OpenWrt-Devel] [PATCH] wireguard: do not add host-dependencies if fwmark is set

2019-03-19 Thread Daniel Golle
The 'fwmark' option is used to define routing traffic to wireguard endpoints to go through specific routing tables. In that case it doesn't make sense to setup routes for host-dependencies in the 'main' table, so skip setting host dependencies if 'fwmark' is set. Signed-off-by: Daniel Golle ---

Re: [OpenWrt-Devel] Broken ipv6 relay

2019-03-19 Thread Hans Dedecker
On Tue, Mar 19, 2019 at 1:53 PM Ansuel Smith wrote: > > Can someone take a look at this bug? Real job is keeping me busy; when I have time I will look into this Hans > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.

[OpenWrt-Devel] Broken ipv6 relay

2019-03-19 Thread Ansuel Smith
Can someone take a look at this bug? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [RFC] ath79: add support for COMFAST CF-E313AC

2019-03-19 Thread Roger Pueyo Centelles
Hi, I've just added support for the COMFAST CF-E313AC, an outdoor wireless CPE with two Ethernet ports and a 802.11ac radio (see patch below). Everything is working fine but I've got two issues for which I'd like to get some advise: 1) target/linux/ath79/base-files/etc/hotplug.d/firmware/11-ath

Re: [OpenWrt-Devel] [PATCH] [odhcp6c] ra: clear RA information and request new after link-up event or SIGUSR2

2019-03-19 Thread Pavel Merzlyakov
>why is this not the case in your setup ? Because sometimes odhcp6c miss restart, probably because of Bridge Mode (it's attached to bridge interface). Anyway, I use a hotplug script which sends SIGUSR2 signal to odhcp6c on link-up event. Of course I could send SIGTERM, but I think it's not the pro

Re: [OpenWrt-Devel] Meson/Ninja build system

2019-03-19 Thread Felix Fietkau
On 2019-03-18 14:03, Jo-Philipp Wich wrote: > Hi, > >> I think the cmake.mk-link approach would be a good idea and given >> previous discussions the plan is afaik to pull in Ninja first and >> once that's confirmed working via CMake add support for Meson. > > fine with me. > >> Having a look a

Re: [OpenWrt-Devel] [PATCH] [odhcp6c] ra: clear RA information and request new after link-up event or SIGUSR2

2019-03-19 Thread Hans Dedecker
Hi, On Mon, Mar 18, 2019 at 8:51 PM Pavel Merzlyakov wrote: > > Hi, > > >Can you be elaborate more in detail what use case you want to cover > >with this patch; in other words what is not working now ? > Ok, > my setup: > Two peer routers A and B which both connected to gateway C. > Routers A and