AR-1 - Adding support category for distributions
AR-4 - Remove Allwinner legacy
AR-5 - Drop Udoo family and move Udoo board into newly created imx6 family
AR-9 - Rename sunxi-next to sunxi-legacy
AR-10 - Rename sunxi-dev to sunxi-current
AR-11 - Adding Radxa Rockpi S support
AR-13 - Rename rockchip64-default to rockchip64-legacy
AR-14 - Add rockchip64-current as mainline source
AR-15 - Drop Rockchip 4.19.y NEXT, current become 5.3.y
AR-16 - Rename RK3399 default to legacy
AR-17 - Rename Odroid XU4 next and default to legacy 4.14.y, add DEV 5.4.y
AR-18 - Add Odroid N2 current mainline
AR-19 - Move Odroid C1 to meson family
AR-20 - Rename mvebu64-default to mvebu64-legacy
AR-21 - Rename mvebu-default to mvebu-legacy
AR-22 - Rename mvebu-next to mvebu-current
AR-23 - Drop meson64 default and next, current becomes former DEV 5.3.y
AR-24 - Drop cubox family and move Cubox/Hummingboard boards under imx6
AR-26 - Adjust motd
AR-27 - Enabling distribution release status
AR-28 - Added new GCC compilers
AR-29 - Implementing Ubuntu Eoan
AR-30 - Add desktop packages per board or family
AR-31 - Remove (Ubuntu/Debian) distribution name from image filename
AR-32 - Move arch configs from configuration.sh to separate arm64 and armhf config files
AR-33 - Revision numbers for beta builds changed to day_in_the_year
AR-34 - Patches support linked patches
AR-35 - Break meson64 family into gxbb and gxl
AR-36 - Add Nanopineo2 Black
AR-38 - Upgrade option from old branches to new one via armbian-config
AR-41 - Show full timezone info
AR-43 - Merge Odroid N2 to meson64
AR-44 - Enable FORCE_BOOTSCRIPT_UPDATE for all builds
* Fix wifi
patch "board-h2plus-nanopi-duo-add-device.patch": increase post-power-on-delay-ms from 50ms to 200ms in wifi_pwrseq node in nanopi-duo dts [dev-branch].
Change in line with other XRADIO device trees (orange pi zero, sunvell).
See also Pull Request #1605.
* Fix xradio patch (dev-branch)
fix KConfig to 5.x - WLAN_VENDOR-flag set to "y" in line with other drivers - otherwise module not loaded.
* correct device name
change nodes "model" and "compatible" to correct device name (from "NanoPi Duo AIR" to "NanoPi Duo") [dev-branch]
Not functionally necessary, but more correct.
* Initial commit for serial consoles rfc
* Board configuration cleanup + small tweaks
* Add serial gadget rename to dev kernel as well
* Cleanup, fixing permissions
* Cleanup board configs
* Initial commit for FA ZeroPi.
* Tested for building.
* Adjust few bugs.
* Move to WIP since its not tested on hardware yet.
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
In current kernels (both next and dev) this patch breaks cpufreq and all that depends on it (no dvfs means board overheating). Removing it makes cpufreq and dvfs work again.
I've tested my OPi3 for best voltage numbers (for resolving stability problem after first patch), using StabilityTester and increasing slowly mV by 10 after every crash. Finaly, this values gives no error by running StabilityTester 100 times.
new values are based on stabilityTester results
when using 930mV for 1.6GHz and 980mV for 1.8GHz, xhpl failed randomly.
So 930/980mV are the critical operation voltage.Then increase 10mV and
run 100 times test, result shows that xhpl (not always) failed 1~2 times.
It seems +10mV is still not enough to ensure dc-dc output voltage always
above operation voltage, that means the design of dc-dc converter is not
good enough that results in large ripple.
The testing script is "github.com/mzhboy/StabilityTester"
The following configuration have been tested.
1.08-1.32-1.48-1.64-1.8 GHz
900-910-920-930-990 *ok, 930 failed 2/100
900-900-910-940-990 *ok, 990 failed 1/100
890-900-910-940-990 *ok, 990 failed 1/100
880-880-910-940-1000 *ok, 940 failed 2/100
880-880-910-950-1000 *ok, 1000 failed 1/100
880-880-910-950-1010 *ok
use more powerfull 'cpuburn-a53' to do pressure test.
power meter shows that 'cpuburn-a53' consumes much more power than
'stress -c 4' in the same condition. 930mV is not enough when running
'cpuburn-a53' meanwhile 950mV is the minimum voltage.
When running 'cpuburn-a53' at 1.8G, h6 consumes lots of power and generate
such amount of heat that an active cooling is necessary otherwise h6
gets overheat and system crashes. Even with active cooling and heatsink
is in low temperature the junction temperature is still quit high that
it reaches about 88~90 ℃ . Maybe the high thermal resistance of plastic
package causes the problem.
* [sunxi-dev][h6]update orangepi lite2 dts file patch
* [sunxi-dev][h6]update patch for sun50i-h6.dtsi
* [sunxi-dev][h6] new operation voltage table of allwinner h6
The correct operation voltages are find out after many reboots and test (over 20+).
the original 1.16v@1.64/1.8GHz was too high since standard cell voltage
of 28nm@HPC is 0.9v, h6 got overheat very quickly over 110 Celsius and then system hangs,
a power-cycle off is needed to reset soc.
I use 'stress -c 4' to do pressure test, with a medium size passive heatsink on top of h6.
The pressure test proves that the soc has about 4 watt power consuming
that is much lesser than original 6~7.x watt when running at 1.8GHz(orangepi lite2 with
usb Ethernet rtl8153 and usb hub, wifi is connected but not used).
Soc runs much more stable and does not get overheat easily under heavy load
with new opp table.
* [sunxi-dev][h6] orangepi lite2 wifi fix
bcm43455-fmac is buggy, reset to bcm4329-fmac
