Re: [OpenWrt-Devel] [LEDE-DEV] Remerge logo ideas

2017-05-29 Thread Jamie Stuart 
See another iteration, with:

- correct capitalisation
- antenna to the side (will not work with lowercase ’n’)
- open sans typeface (open source)
- mockups of website header
- accent colours

http://i.imgur.com/ZKtcFXo.png


> On 29 May 2017, at 13:52, John Crispin <j...@phrozen.org> wrote:
> 
> 
> 
> On 29/05/17 12:11, Jamie Stuart wrote:
>> Hi,
>> First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
>> moving forward.
>> For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - 
>> and not tied to the name of an old router!)
>> 
>> However, it seems the consensus is that the OpenWrt name should remain. I 
>> thought that maybe we should take this opportunity to at least give the 
>> project an updated look?
>> Maybe a new logo? I’m personally not one for mascots, so I had a quick go at 
>> a few simple text-based designs:
>> 
>> http://i.imgur.com/9zyXSYR.png
>> 
>> What are you thoughts?
>> 
>> Jamie, onebillion
> 
> Hi,
> 
> the correct spelling is OpenWrt with a capital O and W. could you add that to 
> the proposal aswell please ? ideally with and without the antenna feature
> 
>John
>> ___
>> Lede-dev mailing list
>> lede-...@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/lede-dev
> 
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] [LEDE-DEV] Remerge logo ideas

2017-05-29 Thread Jamie Stuart 
Hi,
First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
moving forward.
For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - and 
not tied to the name of an old router!)

However, it seems the consensus is that the OpenWrt name should remain. I 
thought that maybe we should take this opportunity to at least give the project 
an updated look?
Maybe a new logo? I’m personally not one for mascots, so I had a quick go at a 
few simple text-based designs:

http://i.imgur.com/9zyXSYR.png

What are you thoughts?

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

[OpenWrt-Devel] [LEDE-DEV] MT7620A WiFi issue - with a twist!

2017-02-01 Thread Jamie Stuart 
Hello LEDE / OpenWRT devs,

I am requesting your help. First a little background…

I am co-founder of an education technology charity, onebillion ( 
https://onebillion.org/  ). We build apps that enable 
children to learn to read and become basically numerate in their own language. 
We are working with partners in Malawi and other sub-saharan African countries 
to scale tablet-based learning initiatives to marginalised children through the 
Unlocking Talent Initiative ( https://unlockingtalent.org 
 ). Working through government schools in Malawi, 
groups of 30 children at a time are learning through our apps using 
solar-powered tablets. There are 120 schools (and rising) across the country 
taking part in the initiative. As of today, 20,000 children are getting 
numeracy and reading lesson in their own language every week.


In each school, the children’s tablets are connected via wifi to a small server 
to store their progress. It has a 3G connection to allow remote monitoring and 
MDM commands to be sent to the children’s tablets. The server ( 
http://www.zbtlink.com/products/router/WE1026.html 
 ) currently runs OpenWRT 
(DD, from source, with a number of packages including MySQL, nginx, php7, 
OpenVPN,).

However…

We have a persistent problem. The tablets frequently have trouble communicating 
with the server over WiFi. We have replicated this issue in our London office 
using 30 iPad Minis connected to a test server. After running for a while (and 
especially during periods of high network activity, which are sparse), these 
errors appear in the logs:

rt2800mmio_txstatus_is_spurious: Warning - 4 spurious TX_FIFO_STATUS 
interrupt(s)
rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
rt2800mmio_txdone: Warning - Got TX status for an empty queue 2, dropping


After that, data transfer between client and server either slows to a crawl or 
stops entirely and the client decides to disassociate. This is not good for the 
children as we lose the ability to monitor their progress, and for them to log 
in.


This a known issue with the chipset and seems to have been round for years.
We are currently building on LEDE trunk and still the issue persists.

We are not driver developers, so my question is whether anyone with knowledge 
can help and provide a proper fix for this issue?

Jamie, onebillion







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

[OpenWrt-Devel] [PATCH] ramips: Added support for ZBT-826 / ZBT-1026

2016-02-29 Thread Jamie Stuart 
V2 - corrected alphabetic ordering
Support for these MT7620-based routers: https://wiki.openwrt.org/toh/zbt/we-826
Based on Oskari’s patches found here: https://dev.openwrt.org/ticket/19996
Tested on we-1026 and we-826-T


---
diff --git a/target/linux/ramips/base-files/etc/board.d/01_leds 
b/target/linux/ramips/base-files/etc/board.d/01_leds
old mode 100755
new mode 100644
index d1b4e15..8fd50fe
--- a/target/linux/ramips/base-files/etc/board.d/01_leds
+++ b/target/linux/ramips/base-files/etc/board.d/01_leds
@@ -268,6 +268,11 @@ zbt-wa05)
set_wifi_led "$board:blue:air"
set_usb_led "$board:blue:usb"
;;
+zbt-we826)
+   ucidef_set_led_default "power" "power" "$board:green:power" "1"
+   set_wifi_led "$board:green:wifi"
+   set_usb_led "$board:green:usb"
+   ;;
 zbt-wr8305rt)
ucidef_set_led_default "power" "power" "$board:green:sys" "1"
set_usb_led "$board:green:usb"
diff --git a/target/linux/ramips/base-files/etc/board.d/02_network 
b/target/linux/ramips/base-files/etc/board.d/02_network
old mode 100755
new mode 100644
index 0121e51..0a680d0
--- a/target/linux/ramips/base-files/etc/board.d/02_network
+++ b/target/linux/ramips/base-files/etc/board.d/02_network
@@ -209,6 +209,7 @@ ramips_setup_interfaces()
ucidef_add_switch "switch0" \
"1:lan" "2:lan" "0:wan" "6@eth0"
;;
+   zbt-we826|\
zbt-wr8305rt)
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "6@eth0"
diff --git a/target/linux/ramips/base-files/lib/ramips.sh 
b/target/linux/ramips/base-files/lib/ramips.sh
old mode 100755
new mode 100644
index c6c32fe..c4eb357
--- a/target/linux/ramips/base-files/lib/ramips.sh
+++ b/target/linux/ramips/base-files/lib/ramips.sh
@@ -475,6 +475,9 @@ ramips_board_detect() {
*"ZBT-WA05")
name="zbt-wa05"
;;
+   *"ZBT-WE826")
+   name="zbt-we826"
+   ;;
*"ZBT-WG2626")
name="zbt-wg2626"
;;
diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh 
b/target/linux/ramips/base-files/lib/upgrade/platform.sh
old mode 100755
new mode 100644
index 5575b4c..8742306
--- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
@@ -138,6 +138,7 @@ platform_check_image() {
y1|\
y1s|\
zbt-wa05|\
+   zbt-we826|\
zbt-wg2626|\
zbt-wr8305rt|\
zte-q7|\
diff --git a/target/linux/ramips/dts/ZBT-WE826.dts 
b/target/linux/ramips/dts/ZBT-WE826.dts
new file mode 100644
index 000..22bef99
--- /dev/null
+++ b/target/linux/ramips/dts/ZBT-WE826.dts
@@ -0,0 +1,124 @@
+/dts-v1/;
+
+/include/ "mt7620a.dtsi"
+
+/ {
+   compatible = "zbtlink,zbt-we826", "ralink,mt7620a-soc";
+   model = "ZBT-WE826";
+
+   chosen {
+   bootargs = "console=ttyS0,115200";
+   };
+
+   palmbus@1000 {
+   gpio0: gpio@600 {
+   status = "okay";
+   };
+
+   gpio1: gpio@638 {
+   status = "okay";
+   };
+
+   gpio3: gpio@688 {
+   status = "okay";
+   };
+
+   spi@b00 {
+   status = "okay";
+
+   en25q128@0 {
+   #address-cells = <1>;
+   #size-cells = <1>;
+   compatible = "w25q128";
+   reg = <0 0>;
+   linux,modalias = "m25p80";
+   spi-max-frequency = <1000>;
+
+   partition@0 {
+   label = "u-boot";
+   reg = <0x0 0x3>;
+   read-only;
+   };
+
+   partition@3 {
+   label = "u-boot-env";
+   reg = <0x3 0x1>;
+   read-only;
+   };
+
+   factory: partition@4 {
+   label = "factory";
+   reg = <0x4 0x1>;
+   read-only;
+   };
+
+   partition@5 {
+   label = "firmware";
+   reg = <0x5 0xfb>;
+   };
+   };
+   };
+   };
+
+   sdhci@1013 {
+   status = "okay";
+   };
+
+   ehci@101c {
+   status = "okay";
+   };
+
+   ohci@101c1000 {
+   status =

[OpenWrt-Devel] [PATCH] Ralink RT288x/RT3xxx: Added support for ZBT-826 / ZBT-1026

2016-02-29 Thread Jamie Stuart 
Support for these MT7620-based routers: https://wiki.openwrt.org/toh/zbt/we-826
Based on Oskari’s patches found here: https://dev.openwrt.org/ticket/19996

Signed-off-by: Jamie Stuart <ja...@onebillion.org>

---

diff --git a/target/linux/ramips/base-files/etc/board.d/01_leds 
b/target/linux/ramips/base-files/etc/board.d/01_leds
old mode 100755
new mode 100644
index d1b4e15..8fd50fe
--- a/target/linux/ramips/base-files/etc/board.d/01_leds
+++ b/target/linux/ramips/base-files/etc/board.d/01_leds
@@ -268,6 +268,11 @@ zbt-wa05)
set_wifi_led "$board:blue:air"
set_usb_led "$board:blue:usb"
;;
+zbt-we826)
+   ucidef_set_led_default "power" "power" "$board:green:power" "1"
+   set_wifi_led "$board:green:wifi"
+   set_usb_led "$board:green:usb"
+   ;;
zbt-wr8305rt)
ucidef_set_led_default "power" "power" "$board:green:sys" "1"
set_usb_led "$board:green:usb"
diff --git a/target/linux/ramips/base-files/etc/board.d/02_network 
b/target/linux/ramips/base-files/etc/board.d/02_network
old mode 100755
new mode 100644
index 0121e51..0a680d0
--- a/target/linux/ramips/base-files/etc/board.d/02_network
+++ b/target/linux/ramips/base-files/etc/board.d/02_network
@@ -209,6 +209,7 @@ ramips_setup_interfaces()
ucidef_add_switch "switch0" \
"1:lan" "2:lan" "0:wan" "6@eth0"
;;
+   zbt-we826|\
zbt-wr8305rt)
ucidef_add_switch "switch0" \
"0:lan" "1:lan" "2:lan" "3:lan" "4:wan" "6@eth0"
diff --git a/target/linux/ramips/base-files/lib/ramips.sh 
b/target/linux/ramips/base-files/lib/ramips.sh
old mode 100755
new mode 100644
index c6c32fe..8bfa814
--- a/target/linux/ramips/base-files/lib/ramips.sh
+++ b/target/linux/ramips/base-files/lib/ramips.sh
@@ -478,6 +478,9 @@ ramips_board_detect() {
*"ZBT-WG2626")
name="zbt-wg2626"
;;
+   *"ZBT-WE826")
+   name="zbt-we826"
+   ;;
*"ZBT-WR8305RT")
name="zbt-wr8305rt"
;;
diff --git a/target/linux/ramips/base-files/lib/upgrade/platform.sh 
b/target/linux/ramips/base-files/lib/upgrade/platform.sh
old mode 100755
new mode 100644
index 5575b4c..d27d7eb
--- a/target/linux/ramips/base-files/lib/upgrade/platform.sh
+++ b/target/linux/ramips/base-files/lib/upgrade/platform.sh
@@ -139,6 +139,7 @@ platform_check_image() {
y1s|\
zbt-wa05|\
zbt-wg2626|\
+   zbt-we826|\
zbt-wr8305rt|\
zte-q7|\
youku-yk1)
diff --git a/target/linux/ramips/dts/ZBT-WE826.dts 
b/target/linux/ramips/dts/ZBT-WE826.dts
new file mode 100644
index 000..22bef99
--- /dev/null
+++ b/target/linux/ramips/dts/ZBT-WE826.dts
@@ -0,0 +1,124 @@
+/dts-v1/;
+
+/include/ "mt7620a.dtsi"
+
+/ {
+   compatible = "zbtlink,zbt-we826", "ralink,mt7620a-soc";
+   model = "ZBT-WE826";
+
+   chosen {
+   bootargs = "console=ttyS0,115200";
+   };
+
+   palmbus@1000 {
+   gpio0: gpio@600 {
+   status = "okay";
+   };
+
+   gpio1: gpio@638 {
+   status = "okay";
+   };
+
+   gpio3: gpio@688 {
+   status = "okay";
+   };
+
+   spi@b00 {
+   status = "okay";
+
+   en25q128@0 {
+   #address-cells = <1>;
+   #size-cells = <1>;
+   compatible = "w25q128";
+   reg = <0 0>;
+   linux,modalias = "m25p80";
+   spi-max-frequency = <1000>;
+
+   partition@0 {
+   label = "u-boot";
+   reg = <0x0 0x3>;
+   read-only;
+   };
+
+   partition@3 {
+   label = "u-boot-env";
+   reg = <0x3 0x1>;
+   read-only;
+   };
+
+   factory: partition@4 {
+   label = "factory";
+   reg = <0x4 0x1>;
+   read-on