the new cpu opp table in 4.19 now supports frequencies up to 1.368GHz, so this change
updates the 1.3GHz overclock overlay as appropriate. overlay name has been changed
to "cpu-clock-1.3GHz-1.3v" as this overlay is only needed for boards that provide a
fixed-voltage GPIO regulator/switcher that operate at 1.1v/1.3v.
Addresses were wrong, probably a mistake from the 64-bit DTS change for RK3288. This takes care of dmesg errors and reaching the I2C devices onboard.
@miouyouyou
* 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.
- 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, ...
There are two versions of the NanoPi NEO2 board; this change adds the default DT for the
v1.1 board. It includes the correct LED configuration and the MP2143DJ VDD regulator
definition.
This change introduces an optional overlay that can be used to modify
the default CPU clock operating table to support a maximum core clock
of 1.4GHz. These higher clock rates will only be allowed if the
board's CPU VDD regulator can support operation at 1.4v (or greater),
e.g., SY8106A.
This change adds a board configuration for the NanoPi NEO Core2 LTS device ("nanopineocore2").
This board configuration provides support for the Core2's SY8106A I2C-based voltage regulator.
This regulator provides higher CPU voltage operation, allowing higher CPU clock rates to be
utilized.
* [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
the I2S clock is apparently problematic right now, or the dts definition is off. Either way it is causing problems at the moment. This simply doesn't add the device tree entries for the cards.
* 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
renamed board-47-02-enable-dvfs-opi-one from safe-need-more-inspection/47-02-enable-dvfs-opi-one
renamed board-47-05-enable-dvfs-opi-lite from safe-need-more-inspection/47-05-enable-dvfs-opi-lite
renamed board-47-01-enable-dvfs-opi-zero from safe-need-more-inspection/47-01-enable-dvfs-opi-zero
File: unresolved/12-dw-hdmi-add-H3-glue.patch
now included upstream in drivers/gpu/drm/sun4i/Kconfig b/drivers/gpu/drm/sun4i/Kconfig
and in drivers/gpu/drm/sun4i/Makefile
and provided upstream in drivers/gpu/drm/sun4i/sun8i_dw_hdmi.c
* removing unresolved/00-19-add-H3-i2s-DT-nodes.patch
removing unresolved/00-19-add-H3-i2s-DT-nodes.patch
=> now already included into dts/sunxi-h3-h5.dtsi upstream
* removed 00-20-add-i2s-DT-pins.patch
removing 00-20-add-i2s-DT-pins.patch
=> updated and renamed to general-dd-i2s-DT-pins.patch
* updated 00-20-add-i2s-DT-pins.patch
updated 00-20-add-i2s-DT-pins.patch and renamed to general-dd-i2s-DT-pins.patch
=> failed originally because mmc0_pins_a rename ...
