raschid

@Igor quick fix (fix-xradio-interrupt.patch):
diff --git a/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts b/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts index 454408b..df356b5 100644 --- a/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts +++ b/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts @@ -49,6 +49,7 @@ #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> +#include <dt-bindings/pinctrl/sun4i-a10.h> / { model = "Xunlong Orange Pi Zero"; @@ -157,6 +158,10 @@ */ xr819: sdio_wifi@1 { reg = <1>; + compatible = "xradio,xr819"; + interrupt-parent = <&pio>; + interrupts = <6 10 IRQ_TYPE_EDGE_RISING>; + interrupt-names = "host-wake"; }; }; performance is back up to around 10 mbit/s ... (PCB rev 1.1). 

@Igor, sorry, I misspelled "patch" in my original post and I think you copy&pasted that typo when uploading the patch.

the following patch fixes cpufreq for the Orange Pi Zero, Mainline 4.11.12.
@mbee, to give it a try save it as e.g. "orangepi-zero-add-cpufreqscaling.patch" and place it in build/userpatches.
Don't forget to freeze the kernel version in armbian-config to avoid loosing this functionality when running apdate/upgrade.
This patch also fixes some temperature issues since the CPU is not fed 1.3V all the time. My OPiZ is right now idling happily at 30 deg (21 deg ambient temp). Armbianmonitor now reports the current cpu-freq.
@igor, please consider to include this patch. 
diff --git a/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts b/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts index 69b4a35..506c462 100644 --- a/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts +++ b/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dts @@ -50,10 +50,11 @@ #include <dt-bindings/gpio/gpio.h> #include <dt-bindings/input/input.h> #include <dt-bindings/pinctrl/sun4i-a10.h> +#include <dt-bindings/thermal/thermal.h> / { model = "Xunlong Orange Pi Zero"; - compatible = "xunlong,orangepi-zero", "allwinner,sun8i-h2-plus"; + compatible = "xunlong,orangepi-zero", "allwinner,sun8i-h3"; aliases { serial0 = &uart0; @@ -94,6 +95,77 @@ reset-gpios = <&r_pio 0 7 GPIO_ACTIVE_LOW>; post-power-on-delay-ms = <200>; }; + + vdd_cpux: gpio-regulator { + compatible = "regulator-gpio"; + regulator-name = "vdd-cpux"; + regulator-type = "voltage"; + regulator-boot-on; + regulator-always-on; + regulator-min-microvolt = <1100000>; + regulator-max-microvolt = <1300000>; + regulator-ramp-delay = <50>; /* 4ms */ + gpios = <&r_pio 0 6 GPIO_ACTIVE_HIGH>; + gpios-states = <0x1>; + states = <1100000 0x0 + 1300000 0x1>; + }; +}; + +&cpu0 { + operating-points = < + 1008000 1300000 + 816000 1100000 + 624000 1100000 + 480000 1100000 + 312000 1100000 + 240000 1100000 + 120000 1100000 + >; + #cooling-cells = <2>; + cooling-min-level = <0>; + cooling-max-level = <6>; + cpu0-supply = <&vdd_cpux>; +}; + +&cpu_thermal { + trips { + cpu_warm: cpu_warm { + temperature = <65000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_hot: cpu_hot { + temperature = <75000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_very_hot: cpu_very_hot { + temperature = <90000>; + hysteresis = <2000>; + type = "passive"; + }; + cpu_crit: cpu_crit { + temperature = <105000>; + hysteresis = <2000>; + type = "critical"; + }; + }; + + cooling-maps { + cpu_warm_limit_cpu { + trip = <&cpu_warm>; + cooling-device = <&cpu0 THERMAL_NO_LIMIT 1>; + }; + cpu_hot_limit_cpu { + trip = <&cpu_hot>; + cooling-device = <&cpu0 2 3>; + }; + cpu_very_hot_limit_cpu { + trip = <&cpu_very_hot>; + cooling-device = <&cpu0 5 THERMAL_NO_LIMIT>; + }; + }; }; &ehci0 {  

Updated dev / testing image for Opi Zero, wireless + upstream patches included: https://dl.armbian.com/orangepizero/Ubuntu_xenial_dev.7z

OK so now that others see that zero wi-fi is not as crappy as others have stated.
 
I have wireless streamed / transferred 67 gig across a zero this month and did not see any real issues.
 
Now can we get it enabled for all the users??
NOT having it enabled really does not make much sense, if the powers to be do not wish to "support" then don't.
They could move those post to Peer support. Some of us are only looking at IoT projects, moving txt / csv / xml files, and so on.
 
I did a little project a few weeks back, call it a proof of concept, I was sent 10 zero's / sd cards and power supplies purchased as a package deal.
I setup the zeros as asked and they went out to service, the Monkey tech installing the zero's had issues with a cisco catalyst ??, and another cisco switch??.
The "tech" (firedog / geeksquad / Gurus to go) did not know what model switches....
 
He said one zero would not connect (wired), said he had to plug one into the switch with 12 " cable, going thru the punch down block did not work, another he had to use a cheap switch between the zero and cisco. I am told those 2 zeros have heavy packet loss over the wired connection and drop off the network once or twice a day.
Now just to be clear I did not recommend the Zero, I said he should use the PC Plus.
P.S. Because I got paid for this project I donated a small part (about 10%) to Igor..as I used Armbian build for the zeros. Hint... Hint... If everyone did this Igor and ??? could have a weekend long drunk on us.

I confirm that raschid patch worked also for me. It include botth DTS mods for opizero and the patched driver for 4.11.
May thanks for the success.  I will some perfomance test also. As regards distance to AP I think this could be improved with a better antenna. The one that come with the zero seems really low quality,
 
 
 
 

I am fully aware that that there have been issues in the past with some peoples expectations regarding this driver.
But this very thread shows that a significant fraction of users seem to be fine with its limited function and performance.
The download page for the OPi Zero already provides ample warning regarding the "module quality".
 

Nice - that fixed it.
 
[ 74.030917] systemd[1]: apt-daily.timer: Adding 1h 13min 16.687045s random time. [ 177.557914] xradio_wlan mmc1:0001:1: missed interrupt [ 236.371472] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 283.880879] wlan0: authenticate with 80:1f:02:d0:__:__ [ 283.880976] ieee80211 phy0: ignore IEEE80211_CONF_CHANGE_MONITOR (0)IEEE80211_CONF_CHANGE_IDLE (1) [ 283.883019] wlan0: send auth to 80:1f:02:d0:__:__ (try 1/3) [ 283.897534] wlan0: authenticated [ 283.907946] wlan0: associate with 80:1f:02:d0:__:__ (try 1/3) [ 283.911220] wlan0: RX AssocResp from 80:1f:02:d0:__:__ (capab=0x411 status=0 aid=5) [ 283.911463] ieee80211 phy0: vif 0, configuring tx [ 283.911941] ieee80211 phy0: vif 0, configuring tx [ 283.912366] ieee80211 phy0: vif 0, configuring tx [ 283.912788] ieee80211 phy0: vif 0, configuring tx [ 283.915753] wlan0: associated [ 283.915973] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 284.018331] ieee80211 phy0: CCMP_PAIRWISE keylen=16!  
No more "xradio_wlan mmc1:0001:1: received frame has no key status" message spamming the logs.
 
Great. Thx, Zador
 
 

I hope so.
You could try my userpatch until he does:
https://drive.google.com/file/d/0B47UwibE8mfvRXYzR0p4SGJ4Vnc/view?usp=sharing
Copy it to userpatches/kernel/sun8i-dev/
Don't forget to set KERNEL_CONFIGURE="yes" and set XRADIO to manual (m).