- update to latest patchset from Baylibre
- Some bugs addressed
- Open items:
- HDMI does not want to work on boot
- If a "problematic" monitor is present at boot HDMI will not respond to replug
- changing monitors after boot results in 1/2 of the display appearing, second replug and it's ok.
- Changing HDMI resolution results in corrupted screen (aliasing, static, "lines" etc.)
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
Adds preliminary patches for 4.19
Known Issues:
- Does not like a lot of HDMI adapters
Needs tested by anyone with a Le Potato, Odroid C2, or Nanopi K2
- update patchset to reflect @superna9999 's meta-meson patches
- notable update adds video decoder and canvas drivers
As always many thanks to BayLibre and Neil Armstrong
This change brings in the Rockchip version of the FUSB302 USB controller driver into
the kernel (with appropriate changes to enable it to build in kernel 4.19.y), and
configures the module build for the rk3399 kernel. This provides proper operation
of all <&fusb0> "extcon" references for the rk3399-nanopi4 boards, thereby enabling
all board USB host ports (e.g., now including <&u2phy0>) to now function properly.
Reason for disabling Realtek 8822 SDIO Wifi driver: https://github.com/rockchip-linux/kernel/issues/114
GCC 7 (with -Wmisleading-indentation) discovered programming mistakes in Realtek SDIO Wifi drivers. As these drivers are not really required for Rockchip64 devices, building them for default Linux kernel has been disabled until Realtek provides fixed drivers.
- Fixes horrible screen performance/long boot/etc
- Thank you @Miouyouyou
Current issues:
- No Pulse Audio. Probably related to the I2S issues, needs checked
- General config review needed
- Seems to be topping out at 1.6 GHz
- only known bug so far: Somehow the entire screen has been rotated 180 degrees, making the touch screen not align with the graphics (can rotate in settings)
- probably an easy fix, but finished for tonight.
* Bump to 4.18, removing the obvious, fixing build problems, put some on waiting.
* Pin 4.18 to DEV, rollback 4.14 to NEXT, adjust configs, remove one deprecated patch from NEXT and add board-h3-address-some-stability-issues.patch
* Adjust few boards in development to new reality, removing it from NEXT for now
* Adjust few board configs
* Board config adjustement
* Adjust few boards configs
* Port NeoCore2 and Neo21.1 to 4.14.y
* Adjust board config
* Adjust board config
-- Thanks again to @ntemis for bringing these together and letting me know about it
- Tinker reboot now seemingly solved by a proper method, should no longer require OF workarounds
- various fixes from various sources, see patches for complete information.
- boots, still needs debugging of BT/touchscreen/sound
- some patch warnings exist, again WIP update for those willing to take a look. (@chwe17 perhaps?)
Based on work of David Huang https://github.com/hjc4869 Changed in the transition:
- firefly family was renamed to rk3399, which we actually never started to use. It was made for Odroid N1, which will never be sold
- adjusted compiler toolchain2 parameter
- added standard wireless drivers
- kernel config with the following changes: Docker dependencies, ZRAM, CPUfreq info, ...
- added upstream patches
- made test Ubuntu Bionic desktop and CLI Stretch build, bootlog: http://ix.io/1jVu
TBD: wifi and BT support, mainline kernel, ...
enable the MTD SPI flash configuration in the sunxi-next kernel; this allows on-board
SPI flash to be available via MTD by default when enabling the "spi-jedec-nor" overlay
in the boot configuration.
* [Early WIP] Update sunxi-next to kernel 4.17
* Switch Allwinner 32 and 64bit to U-boot 2018.05
* Adjust patched for 4.17.y / sunxi-next
- adjust both configurations
- removing FAT support from u-boot (breaks if you try to save)
Tested those boards:
Cubietruck: wlan fails http://ix.io/1fYS USB OK, HDMI yes
Bananapi R40: http://ix.io/1fZm USB OK, HDMI yes
Lime A64: USB no, HDMI no, wireless buggy, eMMC yes
Orangepi prime H5: OK http://ix.io/1fZJ DVFS no
Orangepi2e: DVFS OK, HDMI OK, net OK, wifi OK, eMMC ok, http://ix.io/1fZT
* Kernel config update, enabling HDMI on CT+
* Trying to fix A64 HDMI but failed. Fixed M64 ethernet instead
* Update orangepioneplus.wip
* Update orangepioneplus.wip
* Fix H6 build process
* Add regulator bits for Orangepizero+, thanks to @5kft
* add H5 support for optional 1.3v regulator and 1.3GHz operation
This patch adds two optional overlays that can be used to:
1) enable the 1.1v/1.3v regulator on boards that provide the necessary compatible H/W support
2) modify the default CPU clock operating table to add new 1.2GHz and 1.3GHz clocks
Note that the generated regulator overlay will only support boards whose 1.1v/1.3v regulator
is controlled by GPIO PL6.
* updates for the NanoPi NEO Plus2
This change introduces a patch that provides two changes for the NanoPi NEO Plus2:
* Configure the "cpu0" to use the "vdd_cpux" regulator; this enables the ability to use higher CPU clocks
* Correct the configurations of the on-board power and status LEDs
* Adjust nightly building and few boards config cleanup
* implemented improved support for the FriendlyArm NanoPi Fire3
* introduced new WIP board configuration "nanopifire3"
* added and enabled the FA SPU1705 regulator
* enabled CPU-based thermal support
* implemented DT-based DVFS table (400MHz-1.4GHz)
* fixed and updated the thermal table and cooling maps
* added support for the onboard LED
* minor patch cleanup
* Initial commit, cleanup of Rockchip default
* clean up patches:
- 100_DTS_Tinker_opp_LED was splitted into 3 patches
- 100_DTS_opp for opp (adjusted to RKs 3 point description of opp Voltage)
- 110_DTS_8723bs for the wifi driver
-rename of 270-dts-tinker-bluetooth.patch -> 111_DTS_disable_AP6212_bluetooth.patch to keep wifi-chip stuff together
- 120_DTS_led1_heartbeat
- 190_dts_tinker_s_emmc was reworked and splitted
- gpiomem node was removed and has its own patch (260_DTS_gpiomem_node)
- i2c1 node was removed and has its own patch 270_DTS_activate_i2c1
- spi2 part was removed (defined in rk3288.dtsi), default CS will now be CS0 not 1 (no reason to change this)
- vdd_log regulator is removed (the counterpart is missing anyway, and actually disabled in ASUS and Rockchips branch) --> own patch in case it gets activated
- 120_workaround_tinker_board_reboot -> 130_workaround_tinker_board_reboot to get some free numbers... ;)
* Renamed 190_DTS_tinker_s_emmc and splitted into DTS-Part and driver part (191_driver_mmc_adjustment)
* Boots, Still no hdmi console
* Rockchip Kernel config updates
Thanks to @Ntemis for the config options, they fixed the framebuffer
Still have runtime GPU errors related to power model
- merging C2 and Meson family on the source level, C2 is still making own kernels, but sources, patches and configs are the same
- merged boot scripts for meson family. support for non existing legacy kernel was dropped from boot scripts, added UUID support, armbianEnv.txt
- Meson default remain on 4.14.y, NEXT moved to 4.17.y and DEV remains on master
- remove deprecated patches, remove wrong permissions in patches
- tested on C2, K2 and Le Potate. USB troubles are still present and common, while K2 and Lepotato might have boot/reboot troubles on 4.16+
- boards configuration cleanup
- moving K2 to the supported list. It's the same level of support as Le Potato
* Basic armbian services RFC
- tested building and upgrade
- armbian-optimize-hardware and armbian-setup-hardware have still the same content
* fix permissions
* Forther renaming and small fixes
* Odroid C2 NEXT tiny config adjustement to remove errros from bootup and moving u-boot to 2018.05
* More cleanings
* permissions fix
* More cleanup ...
* permi
* Remove few Ubuntu related things, fix permissions
* Further mini improvements
* Fix logrotate compression and permission issues
* Bugfix
* Wrong services setup at package install. fixing
* RAM logging: workaround for older kernel/btrfs driver versions
* Renaming services, proper config for zram, few bugfixes.
* Various fixes
* Various fixes
* No $TMPFILE needed here
* Various fixes
* Lower this so boards with low memory can use it too
* Various fixes
* Adjust logfile to armbian-hardware-monitor.log
* Remove swap file creation
* Fix permissions in all logrotate configs if needed.
* Prevent loading parallel printer port drivers which we don't need here.
