In Debian Stretch, among others, udev's "predictable interface naming" has been
adopted, meaning the onboard ethernet is no longer named eth0, instead it's
"enx00..(mac address bytes)..". Use a udev rule to apply the RPS settings
instead of /sys/class/net/eth0/... which no longer exists.
* helios4: next branch use u-boot 2018
use new u-boot based on upstream 2018
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* helios4: Tweak fancontrol configuration
Adjusted MINSTART and MINSTOP to suit both old and new fan.
Adjusted TEMP threshold so fan would stop or run in minimal speed when
the system idle.
Fixed wrong MINPWM value.
URL:https://wiki.kobol.io/pwm/#configuration-file
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* kernel: mvebu-next: use upstream helios4 dts
Helios4 device tree has been merged on upstream since 4.19.
Rework the patch to produce same device tree.
URL:https://patchwork.kernel.org/patch/10449393/
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Helios4: Use boot-mvebu-next bootscript
Use boot-mvebu-next.cmd that make use of upstream's Generic Distro
Configuration.
Since loadaddr and fdt_addr varibales are no longer required, remove the
patch.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Helios4: mvebu-next: Add workaround for SPI and SATA concurrent access issue
Concurrent access on SPI NOR and SATA drives can lead to unstable SATA.
Therefore as workaround, disable SATA controller when SPI flash access
is needed and make it as user configurable item in armbianEnv.txt
This workaround might applies to Clearfog too.
Refer to
Commit 59af84c07c ("Helios4: Add SPI bootloader install feature
(#1126)")
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Bootscripts: Fixed boot-mvebu-next.cmd
The environment setting (armbianEnv.txt) is loaded to RAM located on
${load_addr} but the env import use wrong address (${pxefile_addr_r}).
bootargs still expect ${boot_interface} which carried over from boot-
marvell.cmd. Upstream's distro configuration use ${devtype} instead.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
This merge request contains various files which add support for xt-q8l-v10 boards (TVBox) equipped with Rockchip RK3288 SoC, AP6330 WiSoC (BCM4330 WiFi + Bluetooth), 2 GB DRAM (LPDDR2 or DDR3), 8 Gb eMMC, Gigabit Ethernet, 3 USB (1 OTG), 1 microSD slot, SPDIF optical output, 1 HDMI.
Kernel patches:
This thouches all three linux-rockchip-* kernelconfigs, just adds brcmfmac and brcmutil modules and remote controller support. default flavor activates rockchip own remote controller driver, next and dev use the mainline GPIO CIR driver (dev has lirc userland support activated too).
About the remote controller, an additional kernel module is added to the existing keymaps which is activated via device tree.
About possibly clashing patches assert-phy-reset-when-waking-up-in-rk3288-platform.patch should be checked against other rk3288 boards because it addresses an errata in rk3288 which causes the USB Host ports to stop responding when exiting from autosleep. On my device if I connect the first USB device when the system is already running, the USB Host gets stuck without this patch. Probably to work correctly on other platforms the device tree should include the proper reset lines of the USB PHYs (for reference, check patch/kernel/rockchip-dev/xt-q8l-v10-add-device-tree.patch starting from line 869).
Patch 1-2-regulator-act8865-add-restart-handler-for-act8846.patch adds a restart handler which allows reboot using SIPC bit on act8846 power regulator. Possibly MiQi board is affected (is reboot working there?), others (tinkerboard) should not care.
Patch brcmfmac-add-ap6330-firmware.patch adds firmware file names for ap6330 , should be harmless in other cases.
Patch 0010-GPU-Mali-Midgard-remove-rcu_read_lock-references.patch is from Miouyouyou. It should be harmless, it was suggested by him to do some tests with devfreq
Other patches just add the proper device trees, Kconfig and bits for supporting the board as a regular kernel supported board and should not interfere with anything else
U-Boot patches:
All the patches for u-boot are per-board, so nothing is added which may interfere with other existing boards here. They include the device tree and u-boot config and also a couple of patches to support the silergy power regulators driving current to CPU and GPU
* Initial commit to provide kernel and u-boot configuration and device trees for xt-q8-v10 as patches
Modification to rockchip config to add initialization bits for xt-q8-v10
* Committing correct path for rk3288_ddr_400Mhz... rockchip blob, moved assembling into another section to produce
immediately an u-boot working binary
* Enabled broadcom fmac driver in rockchip-next config
* Changed name definition of rk3288-xt-q8-v10 board to "TVBox"
Added bits to include support AP6330 and binary firmwares into the final image
* Fixed device tree file name in related patch, added patching of Makefile to produce the device tree binary accordingly
* Fixed xt-q8-v10 device tree patch
Added brcmfmac driver to rockchip dev and default kernel configs
* Syncing with upstream
* Splitted add-xt-q8... kernel patches into two separate patches
* Fixed bad extension while adding dtb in makefile for rockchip-default configuration
Updated device tree patches for all rockchip confs
* Enable mmc0 and usb in u-boot config
Fixed again makefile patch for kernel next
* Adding patches to reset the USB phy when kernel requires a reset, fixes autosuspend issue
* Changed xt-q8-v10 to proper xt-q8l-v10 in every string and every filename
Added power hold to u-boot, so now the device will boot and stay turned on without the need for the OTG cable anymore
* Changed names from 'Q8' to proper 'XT-Q8L-V10' in device tree patch files
* Legacy kernel device tree:
Fixed bluetooth gpio pin clashing
Fixed HDMI gpio pin clashing
Added support for PWM-based IR-Receiver, added driver in kernel default config too
Various other fixes to avoid some complaints from the kernel
* Added booting bluetooth systemd service for AP6330 (xt-q8l-v10) that loads patchram and invokes hciattach
Minor fixes to -next and -dev device trees for xt-q8l-v10
* Disabled OTG USB port in u-boot due to long timeout during initialization
Fixed warning during u-boot dts compilation
Added emmc as second boot device in dts
* Adding myself to licensing
* Committing modifications to device trees
* Fixed dmac_bus_s explicitly set to unused dmac, restored right dmac in xt-q8l-v10 dts only
Change PLL_CPLL frequency in device tree to 408 Mhz to avoid fractional divisor warnings
* Added proper xt-q8l-v10_rk3288 configuration to u-boot, now appearing in config menu and
correctly selectable as a real target
Fixed typo in device tree from rockchip
* Fixed missing semicolon in device tree for default configuration
Fixed patch files for u-boot appending themselves to files on each compilation
* Added bits to enable power to USB ports in u-boot, thus enabling booting from USB devices (only USB host port for now)
* Changed u-boot binary creation using the rockchip SPL properly
* Added boot order for xt-q8l-v10: sdcard, usb0, eMMC, network
* Added bionic:next in beta config for xt-q8l-v10 board
* Changed some minor bits in xt-q8l-v10 device tree files, added missing bits to dev flavour
Added patches to introduce fairchild fan53555/silergy82x regulators to u-boot and enabled in xt-q8l-v10 device tree
* Updated u-boot to version v2018.03 for xt-q8l-v10. Other rk3288 boards will gain v2018.05 from main armbian fork
Removed pre-reloc labels in u-boot device tree because they are not necessary since we don't use u-boot SPL for xt-q8l-v10
Removed vmmc-supply and vqmmc-supply in u-boot device tree to avoid hang on boot
* Tidied up a bit device trees, in particular some modifications are made to power regulator properties comparing them against the original q8l device tree
Removed unnecessary dummy regulator, removed unnecessary capacities to embedded eMMC
Disabled unused USB host
Removed vmmc-supply and vqmmc-supply from emmc section because it causes hang in u-boot v2018.03 and newer
* Restored previous regulator in u-boot dts
removed assert phy reset USB patch from rockchip-dev because of some upstream incompatible changes
* Added patch to enable IRQ for Midgard drivers which caused massive slowdown on dev kernel
Changed u-boot if-code for xt-q8l-v10 in rockchip.conf
Removed references to rk3288-linux.dtsi in xt-q8l-v10 device tree for default kernel
* Committing effective removal of USB reset assert for dev kernel
Committing changes to u-boot device tree
* Added patch to disable USB power down for rockchip devices broken on latest kernel
* Removed usb dwc2 patch to reinject it from specific branch
* Reverting some voltage changes for xt-q8l-v10 device in rockchip-dev
* Reverting some voltage changes for xt-q8l-v10 in u-boot section
* Added patch to make USB ports working again on rockchip devices with mainline
kernel >= 4.18
* Changed the 0 into false
* Moved xt-q8l-v10 u-boot patches into board_xt-q8l-v10 directory
* Changed some minor things in rockchip-dev dts for xt-q8l-v10, added mali midgard driver to dev kernel config
* Added devfreq support for Mali in rockchip-next flavour
* Remove manually applied patch (0007-drivers-drm...) because it has been
added to armbian main repo
* Removed duplicate patch which has added to main armbian repository
* Tidied up regulators for default/next/dev rockchip flavours for xt-q8l-v10, disabling those regulators which are not tied to anything
Enabled voltage regulator to make SPDIF connector work (thus not tested because I have no DAC)
Changed rockchip-dev and rockchip-next config files to enable gpio-ir-receiver module to enable bundled remote IR controller, including kernel patch for keymap
* Enabled back regulator REG7 to allow propert bluetooth functionaly
* Minor changes to u-boot device tree for xt-q8l-v10
Added patch to set act8846 SIPC to correctly reboot the device (thus require some power-hold at reboot to make reboot fully working)
* Fixed u-boot device tree
* Added configuration bits to support TPL in u-boot for xt-q8l-v10 (TPL is thrown away though) to allow faster reboot times and achieve a working reset feature activating power hold gpio pin as soon as possible. gpio pin is hardwired into spl_board_init() u-boot code because it is not possible to let it work via device tree
Fixed OTG USB port in u-boot, allowing devices detection and booting
Added proper vbus-supply properties for USB controllers in u-boot dts, so u-boot activates USB vbus itself
* Fixed dts makefile patching for next and dev rockchip kernel
* Fixed fdt_file renamed to fdtfile in armbianEnv.txt
* Changed xt-q8l-v10 board config as per recomendations
* Moved xt-q8l-v10 configuration to CSC
Restored linux-rockchip-* configurations, enabled brcmfmac driver, GPIO remote controller driver and lirc kernel compatibility interface
Polished a bit rockchip.conf
* Add patch to brcmfmac driver to search for ap6330 firmware
Removed copy-work from rockchip.conf about ap6330 firmware for xt-q8l-v10 and tidied up
Avoid using brcm_patchram_plus in ap6330-bluetooth-service putting proper firmware file in /etc/firmware for hciattach do firmware uploading itself
* Fixed bcm4330 bluetooth firmware linking for hciattach used by ap6330-bluetooth.service
* Removed foreign test patches from xt-q8l-v10 u-boot directory
* Initial commit BPi R2:
Currently working/not working:
- u-boot:
- builds with minor issues
- patching and cleanup happens on 'https://github.com/chwe17/u-boot-mt'
- next (https://github.com/frank-w/BPI-R2-4.14)
- boots with minor issues
- ETH doesn't work with nm
- sata works
- no wifi (needs driver from: https://github.com/frank-w/BPI-R2-4.4)
- USB not working (xhci-mtk 1a1c0000.usb: fail to get vbus) needs investigation
- appended device tree is needed due to u-boot doesn't work with fdt (kernelpacking needs adjustemts e.g. cat zImage dtb > zImage-dtb
- dev (kernel.org master)
- untested, needs adjustments in config (e.g. CONFIG_LOCALVERSION="")
- since no defconfig is available config is based on frank-w 4.16 Kernel
- Kernel builds without issues
- manual packing of kernel and dtb similar to next
The board boots, serial console is available but everything else must be expected as not working!
- to do:
- u-boot needs a cleanup
- binary blobs needs investigation
- eMMC is **not tested** and needs for sure adjustements! (don't try nand-sata-install!!!)
- bootscript isn't tested (only manual boot over u-boot console at the moment)
- both kernelconfigs aren't 'armbian standard' modules need to be adjusted
Only use it when you know're familiar with u-boot commands!
* Small fixes, add bootscript
- add bootscript for patched u-boot (needs patching of u-boot, currently under investigation and not working properly)
- revert cat zImage dtb > zImage-dtb (cause not working)
- first cleanup of dev kernelconfig (remove CONFIG_LOCALVERSION="")
* Minor fixup
-kernelconfig for next was adjustet so that USB is recognized
-firt bootscripts was written to boot with source command (doesn't work 100% reliable)
-slightly adjustd boardconfig (e.g. bootscript)
must still be considered as early wip!
* small update (FDT works now)
-working bootscript
-adjusted boardconfig
-earlyprintk activated in kernelconfig
* First attempt to get ETH working
-all interfaces are bridged together
-performance sucks at the moment (not clear if it's related to insane network configuration or I miss something obvious... :P )
* Major update (see below for changes):
- 4.14 kernel was dropped due to https://forum.armbian.com/topic/7296-bananapi-r2-csc-mt7623-as-new-boardfamily/?do=findComment&comment=55194 and following
- boot.cmd was adjusted to 'clean' mainline behaviour
- next build opition and its defaultconfg was removed (at the moment dev only)
- rework of the network default configuration
- default configuration will be over network.d **not** NetworkManager
- per default all wired interfaces are bridged together to br0 (still wip)
- old 'interfaces' configuration was removed
- boardconfig is adjusted (no desktop until I've prove that HDMI works)
- what works/ not works:
- board boots up without manual u-boot hacking
- SATA, USB3 (massstorage) is tested and works without issues
- due to rework of network configuration this is still wip and must be considered as 'not working'
* moved to network.d for configuration of wired network
- renamed bsp packages
- blacklist wired interfaces for NetworkManager
- defined all wired interfaces as br0 in systemd/network
- defined networkd als default renderer for bionic (not tested yet!)
* The houskeeping commit:
- BOARDFAMILY was renamed to mt7623 instead of mt7623n (including patchfolders etc.)
- Network.d has no fully control over wired networkes (block NM from controll, start networkd on firstrun etc.)
- Further cleanup kernelconfig
- CPU temp is visible from userspace
- missed switch driver loaded
- cryptodrivers are there (not tested)
- still a bunch of work
* Add DMA mem alloc patch
-under testing!
* Add next option (4.17.y) stick dev to master (4.18-rc1 untested)
* minor fixes:
- solve kconfig issues between 4.17 and 4.18
- stick next branch to 4.18
- first attempts to bring up gmac2 (doesn't work currently)
* switch to upstream u-boot
- fix ext4 dependency in patch series
- kernelpacking currently broken
* add bootz & cmd_ext4
* resolved merge conflict
* apply ugly u-boot patch, fix bootscript
* remove unneeded stuff, apply forgotten stuff
* update config for dev & clean up boardconf (remove xenial)
* - drop dev and next, move into default. There is no intention to provide stock kernel
- fixed board description, renamed to WIP, where it can be merged later
- packing boot firmware to the u-boot package
- docker dependencies (aufs will be added later. not essential)
- attached to 4.19.y
- loading armbianEnv.txt
- UUID support (tested)
- enabled ZRAM (tested)
- enabled eMMC install (not quite working properly yet)
- Bionic has some issues with systemd networking.
* gov to ondemand (thermals are conservative anyway), remove unneeded kernelconfigs
* Added AUFS, remove debug from kernel boot parameters, add ath10 mPCI support (which works)
* add power-off-key and rtc
* Added onboard wireless, but it's enabling is disabled by default. Too fragile.
* Change to CSC target
* Helios4: Add workaround for SPI and SATA concurrent access issue
Concurrent access on SPI NOR and SATA drives can lead to unstable SATA.
Therefore as workaround, disable SATA controller when SPI flash access
is needed and make it as user configurable item in armbianEnv.txt
This workaround might applies to Clearfog too.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Helios4: Add U-Boot SPI
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* Helios4: Add SPI bootloader install feature
This will allow to use nand-sata-install to perform the following operations on Helios4 :
- Install bootloader to SPI NOR Flash (Option 5 in Menu).
- Copy RootFS to USB storage in order to boot from SPI with RootFS on USB (Option 6 in Menu).
* Unmount temp mount points in create_armbian() instead of hardcoded /dev/sda
When using a zram device mounted and formatted as ext4 it should be mounted using
the "discard" option so that the actual allocated memory is freed and returned to
the system when files are deleted.
When using a zram device mounted and formatted as ext4 it should be mounted using
the "discard" option so that the actual allocated memory is freed and returned to
the system when files are deleted (as opposed to just flagging the delete in the
metadata, and leaving the underlying memory still allocated).
When running armbianmonitor -N/n and two or more routable network interfaces are detected create a dynamic dialog box to select which interface should be monitored. Otherwise proceed as usual. Also reverts #1106
