* Initial Mvebu RFC https://github.com/armbian/build/issues/1426
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* mvebu: add missing patches
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* mvebu: change making u-boot targets to standard way, adjust patches and config
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* helios4: set default branch to use U-Boot 2018.11
Switch over to U-Boot 2018.11 that has been used for some time in next
branch.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: Enable DEV branch
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: Add RTC support on Clearfog and Helios4
Added DM driver for mvebu RTC and enable it on Clearfog and Helios4
configuration.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* add boot-marvell.cmd backward compatibility
The patches added missing variable that used on boot-marvell.cmd and
also adjust the some memory addresses to prevent crash due to usage of
fdt_high and initrd_high.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* helios4: Added SPI NOR flash target
Build bootable SPI NOR flash image.
Change the boot order to USB -> SATA -> MMC
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Restore SPI support on U-Boot 2019.04
* mvebu: kernel: Added Wake-On-GPIO and WoL support
The patch set was missing during transition.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* [#1429] SolidRun's ARMADA A388 SOM U-Boot ODT Update
Old versions of U-Boot did not configure correctly the ODT on data
signals of DDR RAM on SolidRun's ARMADA A388 SOMs.
According to SolidRun Knowledge Base, the changes already pushed to
mainline U-Boot. But then it was overwritten when Marvell DDR Training
Tool updated
[URL]
https://developer.solid-run.com/knowledge-base/armada-38x-som-u-boot-odt-update/
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* [#1429] mvebu: u-boot: Add revision id for Armada 38x B0
Added patch for SolidRun U-Boot v2018.01 and
for Helios4 U-Boot v2018.11
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* clearfog: Added SPI NOR flash target
Build bootable SPI NOR flash image.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: clearfog: DEV branch use mainline U-Boot
Also move clearfog base patch into its own board folder.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: enable U-Boot uart target
Normal MMC image can be used for uart boot using following command:
./tools/kwboot -b u-boot-spl.kwb /dev/ttyUSBX
But on Helios4, the SPL failed to continue the booting process if ECC is
enabled, so disable it.
Since the usage of uart boot is more for rescue/debug, disable autoboot.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: NEXT branch use mainline U-Boot
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: fix fancontrol related bug during buster testing
- On kernel 4.19, cpu thermal sensor changed the name from
armada_thermal into f10e4078.thermal. Added this new name to udev rules
- Since DEFAULT branch now use kernel 4.14, update fancontrol
configuration
- Load lm75 kernel module
- On kernel 4.19, cpu temp reading about 20 degree C lower, update
fancontrol configuration.
[URL]
https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: Override vendor provided fancontrol unit
systemd emit following message on dmesg
systemd[1]: /lib/systemd/system/fancontrol.service:9: PIDFile=
references path below legacy directory /var/run/, updating
/var/run/fancontrol.pid \xe2\x86\x92 /run/fancontrol.pid; please update
the unit file accordingly.
Override and change the value in the unit file to remove the message.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: DEV branch use its own u-boot patch folder
The patches are copied over from u-boot-mvebu-next
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: u-boot: Make clearfog model distinction more obvious
While at it, also change SerDes LANE4 into USB 3.0 on Clearfog Base.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* lib: Use apt-get install instead of dpkg on install_deb_chroot()
dpkg -i does not install dependencies required by the package.
This is needed if the BSP package requires other package that is not
installed during debootstrap.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* config: mvebu: helios4: Move various tweak to family_tweak_bsp()
Various tweak in family_tweaks_s() only applied to SD card image.
Move it to family_tweaks_bsp() so it will also included on the BSP
package and applied to existing user.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* config: mvebu: helios4: Add /etc/modules to BSP
On kernel 4.19, user need to modify the /etc/modules to add lm75 kernel
module. Pack the file into BSP so user no longer needed to modify it.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: kernel: Make zbud as built-in module
To remove the following error:
[ 1.705485] zswap: default zpool zbud not available
[ 1.705488] zswap: pool creation failed
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* bootscripts: mvebu: Add default value for spi_workaround
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: kernel: Backport armada_thermal changes to 4.14 (#1452)
On kernel 4.19, armada_thermal driver has been fixed to address
Marvell's Errata #132698 (The changes first appear on LK 4.16). The
result is temperature reading is around 20 degree Celsius lower.
Currently armbian-motd apply -20C tweak for both LK 4.14 and LK 4.19
which is incorrect. Instead of adding some logic on what condition to
apply the tweak, it is better to remove the tweak and patch the kernel
instead.
Revert commit b3dd4e9 ("[ mvebu ] Put back Armada temperature tweak in
motd")
which is part of #1421 solution.
[URL]
https://forum.armbian.com/topic/10214-clearfogpro-possible-change-in-temperature-reporting-between-414next-and-419dev/
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: unified fancontrol config
Since LK 4.14 on DEFAULT branch already patched and the temp reading is
same as LK 4.19 on NEXT branch, it is no longer needed to separate
fancontrol configuration file.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: helios4: Remove rev id patch
The patch is already applied in helios4 repo, no need to have it in
armbian.
This revert helios4 part of commit 7411c55
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: clearfog: enable PCIe support and PCIe reset
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: clearfog: add boot-marvell.cmd backward compatibility
The patches added missing variable that used on boot-marvell.cmd and
also adjust the some memory addresses to prevent crash due to usage of
fdt_high and initrd_high.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu: helios4: tweak regarding temperature setting
Make fan speed similar compared to pre-patched armada-thermal. Target
PWM value around 70 during idle.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* config: sources: clearfog to use u-boot 2018.01 for NEXT branch
This changes also affect Helios4. Moved the shared U-Boot source setting
back to Helios4 for NEXT branch.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* config: boards: build Stretch image for Clearfog and Helios4
Also remove DEV from Helios4 CLI_TARGET
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* kernel: mvebu-next: Disable access to SPI Flash
User need to set spi_workaround=yes to enable SPI Flash access and lost
access to internal SATA.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu-next: adjust kernel config
* mvebu-dev: bump to 5.2 and adjust kernel configuraion. Tested for building.
* Adjust kernel config, add AUFS
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* mvebu-next: Adjust kernel config, add debug GPIO
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* mvebu-dev: separate Clearfog Base U-boot configuration file and patch
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
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.
- change console welcome text
- changed display manager to lightdm by default and remove nodm completly
- desktop login manager enabled by default, toogle can be done with armbian-config
- added URL to the build script and commit hash to /etc/armbian-release file
- added debconf-utils,html2text,mmc-utils,sunxi-tools to the base and additional pkg list
- added synaptic package manager and onboard keyboard to the desktop base
- changed motd console welcome text to: Welcome to Debian Stretch with Armbian Linux 5.1.6-sunxi
- added "logout" to the panel/menu
- added normal users to additional groups: disk tty users games
* Adjust tabs and alter displaying build options at the end - hide empty ones
* Fix wrong MOTD message, adjust logic to autologin by default and request login for both notebooks
* Making fs cache naming more intuitive, rename script
* Move additional kernel drivers into separate file. Add AUFS for K5.1 this way, attach wireguard sources to last known working tag. master is broken atm
* Add two more extra wireless drivers 88x2BU, (improved) 8811EU and introduce switch EXTRAWIFI which is enabled by default
* Move 8812AU to the same version we have now. More recent has some performance issues in AP mode. Adjust configuration, add mvebut-dev 5.1.y kernel
* Enable Wireguard also on 3.10.y since it was fixed upstream. Attach bach to master branch since its working now
* Rockchip64 & RK3399 - upstream patches and remove deprecated patches, mvebu64 add DEV kernel attached to 5.1.y
* Enable BT on Tinkerboard CLI images as well
* cubox-i move to 5.1.y and enable missing HDMI
* Bugfixes for adding wireless driver to Kconfig. Adjusted RK3399 kernel due to upstream changes at FriendlyARM - does not boot yet. Changes has to be extract from their commits. Removed patches with RTL8188EU since we add more recent driver with a new precedure. Small fixes mvebu-default, udoo-next, s56818-next, ... remove deprecated patches.
* Boot-able RK3399-default config, add upstream patches for K4.4.y mvebu-default/udoo-next
* Adjust overclocking patch to meet upstream changes
* Odroid XU4 - remove deprecated kernel patches
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
Commit 683d9384e6 brought back the upstream A64 timer fixes from 5.1.y into to the 4.19.y Armbian NEXT tree but missed the activation in the device node.
This change is the same as commit efff71ba4f for the DEV tree and will re-introduce the activation for the fix.
Add patch to bring A64 pinctrl driver inline with other sunxi pintctrl drivers by disabling strict mode.
With kernel 4.15.y (and later):
* Strict mode was enabled by default via commit 1396007286b1e2fd5dd10ae6a5ccaaaed51ab762 which can/will cause breakage with existing implementations.
* The ability to configure strict mode was added via commit aae842a3ff3385f27f1df8a9ee1494a416ec032d to allow older drivers to maintain existing behavior and avoid breakage.
* Commit cd70387f892205bcd7b8093b0837269b0739cbe0 had then explicitly disabled strict mode for most other existing SoCs but did not include A64.
This change is to update the A64 pinctrl driver similar to the other pre-existing SoC pinctrl drivers.
See 63f8f3badf799c8b63ff33a489886bc138ce5d09 drm: bridge: Constify mode arguments to bridge .mode_set() operation
and fcd70cd36b9bf697122538c9e38e8cf954b2342b drm: Split out drm_probe_helper.h
arch/arm64/boot/dts/allwinner/overlay/sun50i-a64-spi-jedec-nor.dts:12.13-17.6:
Warning (spi_bus_reg): /fragment@0/__overlay__/spiflash: SPI bus unit
address format error, expected "0"
arch/arm64/boot/dts/allwinner/overlay/sun50i-a64-spi-jedec-nor.dts:26.13-31.6:
Warning (spi_bus_reg): /fragment@1/__overlay__/spiflash: SPI bus unit
address format error, expected "0"
Updated DT patch for allwinner unstable timer
Replace previous patch for DT timer node with new patch from upstream commit.
This matches the upstream change to the actual workaround in drivers/clocksource/arm_arch_timer.c
via commit c950ca8c35eeb32224a63adc47e12f9e226da241
