date:20140312

[OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

2014-03-12 Thread José Vázquez Fernández

Add support for Astoria ARV7519RW.

These patches add support for the Astoria ARV7519RW aka Livebox 2.1
The PCI and PCIe interfaces have been disabled. Also, because there are
two revisions of this board with different GPHY firmwares, two targets
were defined.
V2: rewrote partitions to work with an u-boot specifically made for
these boards.

Signed off by: Esteban Benito esteban...@gmail.com
Signed off by: Carles Gadea carles...@gmail.com
Tested by: José Vázquez Fernández ppvazquez...@gmail.com

diff --git a/target/linux/lantiq/base-files/etc/uci-defaults/02_network
b/target/linux/lantiq/base-files/etc/uci-defaults/02_network
index 6e17d4d..a1f7b6a 100644
--- a/target/linux/lantiq/base-files/etc/uci-defaults/02_network
+++ b/target/linux/lantiq/base-files/etc/uci-defaults/02_network
@@ -114,6 +114,11 @@ TDW8970)
lan_mac=$(mtd_get_mac_binary boardconfig 61696)
wan_mac=$(macaddr_add $lan_mac 1)
;;
+
+ARV7519*)
+   lan_mac=$(mtd_get_mac_binary boardconfig 22)
+   wan_mac=$(macaddr_add $lan_mac 1)
+   ;;
 esac
 
 [ -z $(ls /lib/modules/`uname -r`/ltq_atm*) ] || set_atm_wan $vpi
$vci $encaps $payload
diff --git a/target/linux/lantiq/dts/ARV7519RW.dtsi
b/target/linux/lantiq/dts/ARV7519RW.dtsi
new file mode 100644
index 000..7790470
--- /dev/null
+++ b/target/linux/lantiq/dts/ARV7519RW.dtsi
@@ -0,0 +1,186 @@
+/include/ vr9.dtsi
+
+/ {
+
+   model = ARV7519 - Astoria Networks ARV7519RW22-A-LT;
+   
+   chosen {
+   bootargs = console=ttyLTQ0,115200 init=/etc/preinit;
+   };
+   
+   memory@0 {
+   reg = 0x0 0x800;
+   };
+   
+   fpi@1000 {
+   
+   gpio: pinmux@E100B10 {
+   pinctrl-names = default;
+   pinctrl-0 = state_default;
+   
+   state_default: pinmux {
+   mdio {
+   lantiq,groups = mdio;
+   lantiq,function = mdio;
+   };
+   gphy-leds {
+   lantiq,groups = gphy0 led1, gphy1 
led1;
+   lantiq,function = gphy;
+   lantiq,pull = 2;
+   lantiq,open-drain = 0;
+   lantiq,output = 1;
+   };
+   phy-rst {
+   lantiq,pins = io42;
+   lantiq,pull = 0;
+   lantiq,open-drain = 0;
+   lantiq,output = 1;
+   };
+   pcie-rst {
+   lantiq,pins = io21;
+   lantiq,pull = 0;
+   lantiq,output = 1;
+   };
+   };
+   };
+
+   eth@E108000 {
+   #address-cells = 1;
+   #size-cells = 0;
+   compatible = lantiq,xrx200-net;
+   reg =  0xE108000 0x3000 /* switch */
+   0xE10B100 0x70 /* mdio */
+   0xE10B1D8 0x30 /* mii */
+   0xE10B308 0x30 /* pmac */
+   ;
+   interrupt-parent = icu0;
+   interrupts = 73 72;
+
+   lan: interface@0 {
+   compatible = lantiq,xrx200-pdi;
+   #address-cells = 1;
+   #size-cells = 0;
+   reg = 0;
+   mac-address = [ 00 11 22 33 44 55 ];
+
+   ethernet@2 {
+   compatible = lantiq,xrx200-pdi-port;
+   reg = 2;
+   phy-mode = gmii;
+   phy-handle = phy11;
+   };
+   ethernet@3 {
+   compatible = lantiq,xrx200-pdi-port;
+   reg = 4;
+   phy-mode = gmii;
+   phy-handle = phy13;
+   };
+   };
+   
+   wan: interface@1 {
+   compatible = lantiq,xrx200-pdi;
+   #address-cells = 1;
+   #size-cells = 0;
+   reg = 1;
+   mac-address = [ 00 11 22 33 44 56 ];
+

Re: [OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

2014-03-12 Thread John Crispin

hi,

i am starting to wonder if we should to runtime detection of the fw blob
to use ... i.e. indicate in the dts file if we want 11g or 22fe firmware
and let the code figure out the version

John


On 12/03/2014 09:29, José Vázquez Fernández wrote:
 Add support for Astoria ARV7519RW.

 These patches add support for the Astoria ARV7519RW aka Livebox 2.1
 The PCI and PCIe interfaces have been disabled. Also, because there are
 two revisions of this board with different GPHY firmwares, two targets
 were defined.
 V2: rewrote partitions to work with an u-boot specifically made for
 these boards.

 Signed off by: Esteban Benito esteban...@gmail.com
 Signed off by: Carles Gadea carles...@gmail.com
 Tested by: José Vázquez Fernández ppvazquez...@gmail.com

 diff --git a/target/linux/lantiq/base-files/etc/uci-defaults/02_network
 b/target/linux/lantiq/base-files/etc/uci-defaults/02_network
 index 6e17d4d..a1f7b6a 100644
 --- a/target/linux/lantiq/base-files/etc/uci-defaults/02_network
 +++ b/target/linux/lantiq/base-files/etc/uci-defaults/02_network
 @@ -114,6 +114,11 @@ TDW8970)
  lan_mac=$(mtd_get_mac_binary boardconfig 61696)
  wan_mac=$(macaddr_add $lan_mac 1)
  ;;
 +
 +ARV7519*)
 +lan_mac=$(mtd_get_mac_binary boardconfig 22)
 +wan_mac=$(macaddr_add $lan_mac 1)
 +;;
  esac
 
  [ -z $(ls /lib/modules/`uname -r`/ltq_atm*) ] || set_atm_wan $vpi
 $vci $encaps $payload
 diff --git a/target/linux/lantiq/dts/ARV7519RW.dtsi
 b/target/linux/lantiq/dts/ARV7519RW.dtsi
 new file mode 100644
 index 000..7790470
 --- /dev/null
 +++ b/target/linux/lantiq/dts/ARV7519RW.dtsi
 @@ -0,0 +1,186 @@
 +/include/ vr9.dtsi
 +
 +/ {
 +
 +model = ARV7519 - Astoria Networks ARV7519RW22-A-LT;
 +   
 +chosen {
 +bootargs = console=ttyLTQ0,115200 init=/etc/preinit;
 +};
 +   
 +memory@0 {
 +reg = 0x0 0x800;
 +};
 +   
 +fpi@1000 {
 +   
 +gpio: pinmux@E100B10 {
 +pinctrl-names = default;
 +pinctrl-0 = state_default;
 +   
 +state_default: pinmux {
 +mdio {
 +lantiq,groups = mdio;
 +lantiq,function = mdio;
 +};
 +gphy-leds {
 +lantiq,groups = gphy0 led1, gphy1 led1;
 +lantiq,function = gphy;
 +lantiq,pull = 2;
 +lantiq,open-drain = 0;
 +lantiq,output = 1;
 +};
 +phy-rst {
 +lantiq,pins = io42;
 +lantiq,pull = 0;
 +lantiq,open-drain = 0;
 +lantiq,output = 1;
 +};
 +pcie-rst {
 +lantiq,pins = io21;
 +lantiq,pull = 0;
 +lantiq,output = 1;
 +};
 +};
 +};
 +
 +eth@E108000 {
 +#address-cells = 1;
 +#size-cells = 0;
 +compatible = lantiq,xrx200-net;
 +reg = 0xE108000 0x3000 /* switch */
 +0xE10B100 0x70 /* mdio */
 +0xE10B1D8 0x30 /* mii */
 +0xE10B308 0x30 /* pmac */
 +;
 +interrupt-parent = icu0;
 +interrupts = 73 72;
 +
 +lan: interface@0 {
 +compatible = lantiq,xrx200-pdi;
 +#address-cells = 1;
 +#size-cells = 0;
 +reg = 0;
 +mac-address = [ 00 11 22 33 44 55 ];
 +
 +ethernet@2 {
 +compatible = lantiq,xrx200-pdi-port;
 +reg = 2;
 +phy-mode = gmii;
 +phy-handle = phy11;
 +};
 +ethernet@3 {
 +compatible = lantiq,xrx200-pdi-port;
 +reg = 4;
 +phy-mode = gmii;
 +phy-handle = phy13;
 +};
 +};
 +   
 +wan: interface@1 {
 +compatible = lantiq,xrx200-pdi;
 +#address-cells = 1;
 +#size-cells = 0;
 +reg = 1;
 +mac-address = [ 00 11 22 33 44 56 ];
 +lantiq,wan;
 +ethernet@4 {
 +compatible = lantiq,xrx200-pdi-port;
 +reg = 0;
 +phy-mode = rgmii;
 +phy-handle = phy0;
 +};
 +};
 +
 +mdio@0 {
 +#address-cells = 1;
 +#size-cells = 0;
 +compatible = lantiq,xrx200-mdio;
 +phy0: ethernet-phy@0 {
 +reg = 0x0;
 +compatible = lantiq,phy11g,
ethernet-phy-ieee802.3-c22;
 +};
 +phy11: ethernet-phy@11 {
 +reg = 0x11;
 +compatible =

Re: [OpenWrt-Devel] [PATCH] [lantiq] Add support for Astoria ARV7519RW.

2014-03-12 Thread José Vázquez

2014-03-10 12:26 GMT+01:00, José Vázquez Fernández ppvazquez...@gmail.com:
 Add support for Astoria ARV7519RW.

 These patches add support for the Astoria ARV7519RW aka Livebox 2.1
 The PCI and PCIe interfaces have been disabled. Also, because there are
 two revisions of this board with differen GPHY firmwares, two targets
 were defined.

 Signed off by: Esteban Benito esteban...@gmail.com
 Signed off by: Carles Gadea carles...@gmail.com
 Tested by: José Vázquez Fernández ppvazquez...@gmail.com

Esteban Benito wrote an u-boot for this board due to few random
problems found when the stock BRN-boot + u-boot were used.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] [lantiq] Add support for Astoria ARV7519RW.

2014-03-12 Thread José Vázquez

2014-03-12 9:40 GMT+01:00, José Vázquez ppvazquez...@gmail.com:
 2014-03-10 12:26 GMT+01:00, José Vázquez Fernández
 ppvazquez...@gmail.com:
 Add support for Astoria ARV7519RW.

 These patches add support for the Astoria ARV7519RW aka Livebox 2.1
 The PCI and PCIe interfaces have been disabled. Also, because there are
 two revisions of this board with differen GPHY firmwares, two targets
 were defined.

 Signed off by: Esteban Benito esteban...@gmail.com
 Signed off by: Carles Gadea carles...@gmail.com
 Tested by: José Vázquez Fernández ppvazquez...@gmail.com

 Esteban Benito wrote an u-boot for this board due to few random
 problems found when the stock BRN-boot + u-boot were used.
This patch has been marked as superseded because of the aforementioned
bootloader change.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

2014-03-12 Thread José Vázquez

2014-03-12 9:31 GMT+01:00, John Crispin j...@phrozen.org:
 hi,

 i am starting to wonder if we should to runtime detection of the fw blob
 to use ... i.e. indicate in the dts file if we want 11g or 22fe firmware
 and let the code figure out the version

 John


 On 12/03/2014 09:29, José Vázquez Fernández wrote:
 Add support for Astoria ARV7519RW.

 These patches add support for the Astoria ARV7519RW aka Livebox 2.1
 The PCI and PCIe interfaces have been disabled. Also, because there are
 two revisions of this board with different GPHY firmwares, two targets
 were defined.
 V2: rewrote partitions to work with an u-boot specifically made for
 these boards.

You are right: less board definitions, less work and space need for
buildbot and less complications for the people.

Regards:

Pepe
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [PATCHv2] openssl: Fix x86_64 build on some 64bit host systems

2014-03-12 Thread Felix Fietkau

On 2014-03-11 17:42, Helmut Schaa wrote:
 On some build hosts openssl fails to install since openssl installs itself 
 into
 lib64 while the openwrt Makefile expects the libs to end up in lib.
 
 install -m0644 
 .../openwrt/build_dir/target-x86_64_uClibc-0.9.33.2/openssl-1.0.1e/ipkg-install/usr/lib/libcrypto.so.*
  
 .../openwrt/build_dir/target-x86_64_uClibc-0.9.33.2/openssl-1.0.1e/ipkg-x86_64/libopenssl/usr/lib/
 install: cannot stat 
 '.../openwrt/build_dir/target-x86_64_uClibc-0.9.33.2/openssl-1.0.1e/ipkg-install/usr/lib/libcrypto.so.*':
  No such file or directory
 make[2]: *** [/openwrt/bin/x86_64/packages/libopenssl_1.0.1e-2_x86_64.ipk] 
 Error 1
 make[2]: Leaving directory `/openwrt/package/libs/openssl'
 make[1]: *** [package/libs/openssl/compile] Error 2
 make[1]: Leaving directory `/openwrt'
 
 Set LIBDIR accordingly to fix this.
 
 Signed-off-by: Helmut Schaa helmut.sc...@googlemail.com
Committed in r39885, thanks.

- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] bridge operation without physical port, 'bridge_empty'

2014-03-12 Thread Conor O'Gorman


Hi,

I'm trying to get a 'virtual' bridge up to support vlan tagging. But I 
am having great difficulty in making this work. I tried trunk for the 
'bridge_empty' setting, but it's not doing it for me.


Problem is with 'br-lan' not wanting to change to up state:

config interface 'lan'
option type 'bridge'
option bridge_empty '1'
option proto 'none'
option auto '1'

config interface 'vlan10'
option type 'bridge'
option ifname 'wlan0 br-lan.10'
option proto 'none'
option auto '1'

config interface 'vlan20'
option type 'bridge'
option ifname 'wlan0-1 br-lan.20'
option proto 'none'
option auto '1'

The vlan bridges work and do the tagging. If eth0 is added into br-lan, 
that works as a trigger to bring it up.


Am I missing something in the config?

Can I use some other sort of dummy interface to force it up?

Thanks,
Conor
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [RFC] netifd: Reload proto on bridge member add/remove

2014-03-12 Thread Helmut Schaa

Main use-case is to renew/restart DHCP if a bridge member is added/removed.

Signed-off-by: Helmut Schaa helmut.sc...@googlemail.com
---

Maybe it is worth to add another PROTO_CMD_RENEW or something that is more
lightweight instead of running a full setup again?

 bridge.c| 4 
 device.h| 3 +++
 interface.c | 3 +++
 3 files changed, 10 insertions(+)

diff --git a/bridge.c b/bridge.c
index 4ef0d7e..db403c5 100644
--- a/bridge.c
+++ b/bridge.c
@@ -140,6 +140,8 @@ bridge_disable_member(struct bridge_member *bm)
system_bridge_delif(bst-dev, bm-dev.dev);
device_release(bm-dev);
 
+   device_broadcast_event(bst-dev, DEV_EVENT_TOPO_CHANGE);
+
return 0;
 }
 
@@ -162,6 +164,8 @@ bridge_enable_member(struct bridge_member *bm)
goto error;
}
 
+   device_broadcast_event(bst-dev, DEV_EVENT_TOPO_CHANGE);
+
return 0;
 
 error:
diff --git a/device.h b/device.h
index 8d3efa3..e96a4c4 100644
--- a/device.h
+++ b/device.h
@@ -77,6 +77,9 @@ enum device_event {
DEV_EVENT_LINK_UP,
DEV_EVENT_LINK_DOWN,
 
+   /* Topology changed (i.e. bridge member added) */
+   DEV_EVENT_TOPO_CHANGE, 
+
__DEV_EVENT_MAX
 };
 
diff --git a/interface.c b/interface.c
index b2c8baf..7fcc8a0 100644
--- a/interface.c
+++ b/interface.c
@@ -248,6 +248,9 @@ interface_cb(struct device_user *dep, enum device_event ev)
case DEV_EVENT_REMOVE:
new_state = false;
break;
+   case DEV_EVENT_TOPO_CHANGE:
+   interface_proto_event(iface-proto, PROTO_CMD_SETUP, false);
+   return;
default:
return;
}
-- 
1.8.1.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] bridge operation without physical port, 'bridge_empty'

2014-03-12 Thread Conor O'Gorman


On 12/03/14 12:54, Conor O'Gorman wrote:

I'm trying to get a 'virtual' bridge up to support vlan tagging. But I
am having great difficulty in making this work. I tried trunk for the
'bridge_empty' setting, but it's not doing it for me.

Can I use some other sort of dummy interface to force it up?



Kernel veth module is working in this setup. But it seems like a hack.

Thanks,
Conor
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] [RFC] netifd: Reload proto on bridge member add/remove

2014-03-12 Thread Felix Fietkau

On 2014-03-12 14:03, Helmut Schaa wrote:
 Main use-case is to renew/restart DHCP if a bridge member is added/removed.
 
 Signed-off-by: Helmut Schaa helmut.sc...@googlemail.com
 ---
 
 Maybe it is worth to add another PROTO_CMD_RENEW or something that is more
 lightweight instead of running a full setup again?
Yes, please add something like that instead. I would like to avoid going
through a full reconfiguration cycle on every bridge member change.

- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Buildbot confused?

2014-03-12 Thread Hannu Nyman


Looks like the buildbot is confused...

There are only a few March 12th build attemps and still several buildslaves 
sit idle.
Compared to the status a few hours ago, it looks like all not yet started 
builds have been removed from the queue and then buildbot simply waits and 
says that 22.5 hours until the next attempt.


Strangely, the grid display does not show the done 39881 builds.
http://buildbot.openwrt.org:8010/one_line_per_build
http://buildbot.openwrt.org:8010/grid
http://buildbot.openwrt.org:8010/builders

For example thwere has been no March 12th build for ar71xx and still buildbot 
claims that no pending build requests

http://buildbot.openwrt.org:8010/builders/ar71xx

It looks like the buildbot is totally confused :-(
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] ath10k: update firmware and allow choice between AP and STA firmwares

2014-03-12 Thread Matti Laakso

This patch updates ath10k firmware to the latest version, changes the
default firmware to be the one optimized for access point operation, and
introduces a configuration option to choose the client-optimized
firmware instead during build time.

Signed-off-by: Matti Laakso malaakso at elisanet.fi
---

Index: trunk/package/kernel/mac80211/Makefile
===
--- trunk/package/kernel/mac80211/Makefile  (revision 39899)
+++ trunk/package/kernel/mac80211/Makefile  (working copy)
@@ -122,7 +122,7 @@
 $(eval $(call Download,linux-firmware))
 
 PKG_ATH10K_LINUX_FIRMWARE_NAME:=ath10k-firmware
-PKG_ATH10K_LINUX_FIRMWARE_VERSION:=d86e78e5c6be34329936c8bd73a212700437be2e
+PKG_ATH10K_LINUX_FIRMWARE_VERSION:=38eeda3ae6f90fde5546bdd48ee4ff3090f238c0
 
PKG_ATH10K_LINUX_FIRMWARE_SOURCE:=$(PKG_ATH10K_LINUX_FIRMWARE_NAME)-$(PKG_ATH10K_LINUX_FIRMWARE_VERSION).tar.bz2
 PKG_ATH10K_LINUX_FIRMWARE_PROTO:=git
 
PKG_ATH10K_LINUX_FIRMWARE_SOURCE_URL:=https://github.com/kvalo/ath10k-firmware.git
@@ -595,6 +595,19 @@
 PCI is supported.
 endef
 
+define KernelPackage/ath10k/config
+  if PACKAGE_kmod-ath10k
+
+   config ATH10K_STA_FW
+   bool Firmware optimized for STA operation
+   default n
+   help
+ Use the ath10k firmware optimized for wireless client instead 
+ of access point operation.
+
+  endif
+endef
+
 define KernelPackage/carl9170
   $(call KernelPackage/mac80211/Default)
   TITLE:=Driver for Atheros AR9170 USB sticks
@@ -1654,10 +1667,19 @@
 
 define KernelPackage/ath10k/install
$(INSTALL_DIR) $(1)/lib/firmware/ath10k/QCA988X/hw2.0
+ifeq ($(CONFIG_ATH10K_STA_FW),y)
$(INSTALL_DATA) \

$(PKG_BUILD_DIR)/$(PKG_ATH10K_LINUX_FIRMWARE_SUBDIR)/ath10k/QCA988X/hw2.0/board.bin
 \
+   $(1)/lib/firmware/ath10k/QCA988X/hw2.0/
+   $(INSTALL_DATA) \
+   
$(PKG_BUILD_DIR)/$(PKG_ATH10K_LINUX_FIRMWARE_SUBDIR)/main/firmware-2.bin_999.999.0.636
 \
+   $(1)/lib/firmware/ath10k/QCA988X/hw2.0/firmware-2.bin
+else
+   $(INSTALL_DATA) \
+   
$(PKG_BUILD_DIR)/$(PKG_ATH10K_LINUX_FIRMWARE_SUBDIR)/ath10k/QCA988X/hw2.0/board.bin
 \

$(PKG_BUILD_DIR)/$(PKG_ATH10K_LINUX_FIRMWARE_SUBDIR)/ath10k/QCA988X/hw2.0/firmware-2.bin
 \
$(1)/lib/firmware/ath10k/QCA988X/hw2.0/
+endif
 endef
 
 define KernelPackage/mwl8k/install
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Buildbot confused?

2014-03-12 Thread Travis Kemen

I have been working on getting some new infrastructure brought online and
needed to change the configuration. It appears there is a bug in this
version of buildbot when doing a reconfig. I have restarted it now so we
should be back in business.

Thanks,

Travis


On Wed, Mar 12, 2014 at 2:10 PM, Hannu Nyman hannu.ny...@iki.fi wrote:

 Looks like the buildbot is confused...

 There are only a few March 12th build attemps and still several
 buildslaves sit idle.
 Compared to the status a few hours ago, it looks like all not yet started
 builds have been removed from the queue and then buildbot simply waits and
 says that 22.5 hours until the next attempt.

 Strangely, the grid display does not show the done 39881 builds.
 http://buildbot.openwrt.org:8010/one_line_per_build
 http://buildbot.openwrt.org:8010/grid
 http://buildbot.openwrt.org:8010/builders

 For example thwere has been no March 12th build for ar71xx and still
 buildbot claims that no pending build requests
 http://buildbot.openwrt.org:8010/builders/ar71xx

 It looks like the buildbot is totally confused :-(
 ___
 openwrt-devel mailing list
 openwrt-devel@lists.openwrt.org
 https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

Re: [OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

Re: [OpenWrt-Devel] [PATCH] [lantiq] Add support for Astoria ARV7519RW.

Re: [OpenWrt-Devel] [PATCH] [lantiq] Add support for Astoria ARV7519RW.

Re: [OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

Re: [OpenWrt-Devel] [PATCHv2] openssl: Fix x86_64 build on some 64bit host systems

[OpenWrt-Devel] bridge operation without physical port, 'bridge_empty'

[OpenWrt-Devel] [RFC] netifd: Reload proto on bridge member add/remove

Re: [OpenWrt-Devel] bridge operation without physical port, 'bridge_empty'

Re: [OpenWrt-Devel] [RFC] netifd: Reload proto on bridge member add/remove

[OpenWrt-Devel] Buildbot confused?

[OpenWrt-Devel] [PATCH] ath10k: update firmware and allow choice between AP and STA firmwares

Re: [OpenWrt-Devel] Buildbot confused?

13 matches

Site Navigation

Mail list logo

Footer information