* 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
Address 0x44000000 is not available for boards with 1Gb RAM, so it was causing a boot error as described here:
https://forum.armbian.com/topic/5771-rock64-nightly-image/?do=findComment&comment=53150
A lower address 0x39000000 works and doesn't seem to cause any other problem.
I cannot test it in boards with more than 1Gb RAM so, even though I see no reason why it should not be compatible, it is safer to test just in case.
* 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.
