* Add HDMI sound support for Allwinner A10, A20, A31
Closes https://github.com/armbian/build/issues/2084
* Enable HDMI audio in kernel config and update config with misc modules
For some reason these patches are getting applied despite already being in the 5.7 kernel with no complaints from the scripts.
There are more, but it's slow going file by file.
* Bump sunxi to 5.7.y
* Further cleanup 32bit works, 64bit needs more patches adjustement
* Also arm64 boots, SPI flash areas were refactored, new location is a bit fuzzy, leaving behind
* More fixed and cleanings, both variants builds now, but without overlay support
* fix sunxi overlays in AR-329 branch
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
Co-authored-by: Martin Ayotte <martinayotte@yahoo.ca>
* Initial commit for kernel boot splash
* Add startup files to disable bootlog when system is up / down
* Update logo, remove deprecated one
* Introduce new u-boot variable bootlogo
* Adjust kernel config
* Make logo possible on Odroid XU4
- add legacy and current upstream patches
- delete xu4 environment since its not used
* Cleanup C2,C4, both tested, logo works on mainline,
- adding legacy upstream patches for c4
* Enable bootlogo by default on Odroid N2
* Enable logo on RK3399 desktop images
* Cleanup the rest of the environment files
* Add initrd hook that copy splash file to initrd.
* Missing logo bits for one boot scripts
* Enable boot logo on Pinebook A64
* Enable bootlogo on Teres
* Update config
* Adjust Rockchip64 dev and add PBPro stuff
* Remove deprecated patches
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Merge config with current
* WIP: Adding RockpiE config
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Mainline u-boot for ROCK Pi E
* Initial ROCK Pi E device tree in kernel
* Fixed supplies for ROCK Pi E device tree
* Adjusted u-boot load address for rockchip64 boards with 256MB eg. ROCK Pi E
* Blacklisted lima on ROCK Pi E
* Fixed ROCK Pi E patch after merge from master
* Removed mode settings from rk805 regulators
* Fixed issues with offloading for gigabit interface of RockPi E
* Adjusted ROCK Pi E board config
* Added dev branch for ROCK Pi E
* Add build targets
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Exchange legacy to current in ROCK Pi E build targets
Co-authored-by: Piotr Szczepanik <piter75@gmail.com>
* Introducing Rockchip rk322x SoC support
Main features:
- Legacy kernel flavour based upon stable v2.x rk3288 Rockchip branch (https://github.com/rockchip-linux/kernel/tree/stable-4.4-rk3288-linux-v2.x)
- Current kernel flavour based on mainline 5.6.y kernel
- Mainline u-boot (v2020.04)
- Single generic tv box target (rk322x-box) which boots on all the known tv boxes
- Hardware devices (eMMC/NAND, led wiring configuration, SoC variant selection) modulation done by user at runtime via device tree overlays - a script (rk322x-config) is provided for autodetection and simple configuration by inexperienced users;
- Bits added to armbian-hardware-optimization to set affinity for irq handlers
- rk322x-box targets already added to targets.conf for automatic image creation
* Removed disabled patches
* Restored mysteriously removed comment character
* Moved rockchip-dev to kernel 5.7, removed already upstreamed patch (1016), adjusted conflicting patch (1015)
Most kernel configuration answer left at default, notables:
- Wireguard (as module)
- Zswap default compression set to LZO
- RK3288 GPIOMEM (as module)
- Enabled some new DMABUF bits (heaps, cmas)
- Hantro driver
- F2FS compression
* Disabled rx/tx dma for uarts, on my board causes system freeze during bluetooth initialization. Don't know if they ever worked, tried to enable them ages ago and they were already not working
* For xt-q8l-v10 rk3288 board:
- Upgraded u-boot to v2020.04, reworked configuration to match new version, enabled HDMI video console
- Increased u-boot boot delay from 0 seconds to 1 second for rockchip boards, to allow user interrupt u-boot boot process
- Imported efuse rk3288 driver into u-boot, made ethernet address stable using soc serial
- Upgraded ddrbin loader to v1.08
- Added VDSO patch for rockchip-current and rockchip-dev kernels for clock_gettime64 to fix erratic clock on 32 bit ARM devices with recent glibc
- Disabled 600 Mhz OPP node for GPU due to Panfrost instabilities, thus enabled 500 Mhz node
- Various fixes and enhancements to xt-q8l-v10 device trees for current and dev targets
- Added (disabled) u-boot HDMI patch for Tinkerboard
* Removed rk3288 ddrbin v1.08 from rockchip blobs, changed reference to use rkbin-tools repository
* Removed unneeded disabled patch for tinkerboard HDMI
We don't need to enable UARTS and OTG by default on all Nanopi boards. This seems to cause instability on M1
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
NanoPi R2S has the same issue as ROC-RK3328-CC.
With working GPIO, during init the GPIO state s reset.
This causes the sdmmc regulator to shut down, preventing detection.
Removing and replacing the card will allow it to be detected, but that should not be necessary.
Fix this by setting the regulator on at boot.
Signed-off-by: Peter Geis <pgwipeout@gmail.com>
Link: 75aa567803
Signed-off-by: Jayantajit Gogoi <jayanta.gogoi525@gmail.com>
* patch: kernel: rockchip-dev: Handle more resolutions with HDMI (β)
The added patch add more PLL configurations, in order to satisfy
more HDMI frequencies requirements.
This should allow users to benefit from more resolutions.
However, this is fairly untested. I only tested it on my 1080p
screen and, yeah, it works but so does the kernel without this
patch.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
* patch: kernel: rockchip-dev: Handle more resolutions with HDMI (β)
Now with proper patches names.
Anyway :
The added patch add more PLL configurations, in order to satisfy
more HDMI frequencies requirements.
This should allow users to benefit from more resolutions.
However, this is fairly untested. I only tested it on my 1080p
screen and, yeah, it works but it also does without this
patch.
So could anyone test this with the following configurations ?
* [ ] A HDMI 4K screen
* [ ] A HDMI 1366x768 screen resolution
* [ ] A VGA screen with a VGA to HDMI adapter
* [ ] A DVI screen with a DVI to HDMI adapter
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
* Using the patches provided by @Kwiboo for HDMI
This provides me way more resolutions, including interlaced modes.
I don't see 4K modes, though the screen attached can't do it,
so I still don't know if that can help provided 4K modes on mainline
kernels.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
* Support for 4K screens
Using fixes provided by @czak
Tested and approved by @czak too !
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
There have been intermittent issues with SPDIF output on H3 & H2+ devices.
Digging into the H2+ & H3 datasheets I encountered an important clue on
table 8.7.2.2: s_clk needs to be 4x24.576 MHz or 4x22.5782 Mhz.
Probably due to how SPDIF is a huge oversample of the audio frequency.
Co-authored-by: George Lander <lander@jagmn.com>
* Attach Meson64 CURRENT to 5.6.y and make DEV = CURRENT at this point.
There is a lot of changes to 5.7.y and can be done after release or by someone that feels a need for this right now.
* Delete meson64_fclk_div3.patch
this fix has been upstream for some time, I had issues with it on 5.4, which is why it had been removed there.
* [ meson64 current ] kconfig tweak
disable Rockchip SoC drivers
* [ meson64 current ] remove rockchip patches
* [ meson64 current ] disable CMA patch GX
* [ meson64 current] add libretech cc audio patch
This brings the dts even with the khilman 5.8/integ branch which includes all of the audio changes. The kernel is registering audio devices, however nothing comes out. committed in case someone wants to spend time debugging/testing theories.
* fix permissions
was editing from another machine, accidental change of permissions in the patch
* Set default mixer settings
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* [ meson64 current ] GXL audio commit
This moves to the mainline patches and covers le potato and la frite. Adjusted asound config to handle a commonized sound card name.
* [ meson64 current ] add gxbb audio WIP
Playback is too fast, a clock setting is off somewhere.
* Update kernel configs
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
Co-authored-by: Tony <tonymckahan@gmail.com>
* Switching Odroid C1 boot partition to FAT
U-boot FAT driver is very unstable and there is no wish to dig into u-boot. Seems like a sane workaround @plntyk
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Add notes for separate boot partitions
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Typo
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Bugfix: use zImage for converting to uImage since on FAT partitions we use move
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Cleanup C1 boot scripts
We have no plans to ever support legacy kernel again. Removing related things
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* A bit more radical change. Moving meson current to (new) legacy, current to 5.6.y and dev to some development branch / commit.
* Remove unneded patch
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
Enable DMC for roc-rk3328-cc (renegade) in current
No stability issues with this enabled, no reason not to merge, enables higher clockrates via manual setting for now.
* enable and change odroidc1 config
remove EOS
enable current and dev config
meson-current: update config
meson-dev: update config
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* meson-current meson-dev: reduce Kernel size
with default loading locations in u-boot
the uImage can be too large and will be partly overwritten
with the loaded dtb leading to boot failues due to wrong checksum
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* odroid-c1: change default loglevel
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* meson: fix odroidc1 boot and create uImage
without uImage the board will not boot
take the already used hack (?) from
general-kernel-odroidn2-current.patch
since KERNEL_IMAGE_TYPE does not work as expected
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* Update targets.conf
* Update targets.conf
* Update targets.conf
* Making a bigger diff
* Removing build_minimal
One can choose what to build, while build targets are defined elsewhere
* Governor interactive n/a
* Updating config
Cause of changes in boot.ini we don't need to worry about size. After few tests, no problems sighted.
Tested running Docker.
* Adjust dev config too
Tested.
* Update odroidc1.conf
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
deleted activation of i2s1 - 1c2240, because it isnt necessary for the corect operation of audio-analog and sound_hdmi
USB isnt affected.
i2s2 is right, because its needed for sound_hdmi 1c22800
It doesn't want to boot on 5.4.y. Adjusting kernel config, fix Docker dependency problem, move few other minor fixes from openwrt and closing https://github.com/armbian/build/issues/1453
* npi-a64-only-audio-usb.patch
This is a follow-up to the PR #1927 where the complete sun50i-a64.dtsi was changed.
This is a patch ONLY for the NanoPi A64 .dts to activate Audio & Upper USB-port
Has been build/compiled and works with focal 5.6.5
Address = Alias:
sound=sound
sound_hdmi = sound_hdmi
1c19000 = usb_otg
1c22400 = i2s1
1c22c00 = dai
1c22e00 = codec
1c22800 = i2s2
1f015c0 = codec_analog
* Create npi-a64-only-audio-usb.patch
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
* meson-sm1: use amlogic-boot-fip to generate boot binary for SM1
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
* patch: add Linux and U-Boot patches
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
* configs: enable Odroid-C4
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
* Add 8189es out of the tree patch from repository.
* Added 8189FS version
* Support building on kernel 5.6. for 88x2bu
Tested for building on legacy, current and dev, removed old patches
* Cleaned up OrangePi 4 device tree (with help from @chwe17)
* Reconfigured OrangePi 4's usb-c power input
* Powertree fixes for OrangePi 4
* Removed unnecessary xin32k clock in OrangePi 4's device tree
* Reverted fusb302 change for OrangePi 4
* Removed uart4 in OrangePi 4's device tree
* Synced OrangePi 4's DTS from current to dev
* Synced OrangePi 4's DTS from current to legacy
* Minor fixups for OrangePi 4 DTS in legacy
* Add initial support for FriendlyARM Nanopi R2s
One net port not working yet.
* Enable 2nd network, rename it to lan0, adjust motd to see lan*
* Added rk3328 dmc devfreq driver
* Fixed SD card issues for NanoPi R2s
* Added usb serial gadget console for NanoPi R2s
Co-authored-by: Piotr Szczepanik <piter75@gmail.com>
* [ROCK Pi S] WIP mainline (dev) target
* [ROCK Pi S] Disable `rockchip64-dev` patches for now
* [ROCK Pi S] Add rtl8723ds wifi drivers
* [ROCK Pi S] Enable onboard audio (`rk3308-acodec`,`rk3308-i2s-tdm`)
Switch kernelsource to 5.5.y
* [ROCK Pi S] WIP: Use mainline 5.5.y kernel
Add a new `current` branch that tracks mainline
* [ROCK Pi S] Use updated u-boot board dt name `rk3308-rock-pi-s`
Removing the need for a special bootenv for n
* Temporally disable current
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
* kernel: linux-sunxi-{dev,current}: Enable CONFIG_BT_HCIUART_BCM
This patch returns Broadcom's protocol for bluetooth HCI over serial port.
* BananaPiM2Zero: Patches for the devicetree
These patches add HDMI out (with audio) and add bluetooth / wifi
rfkill devices.
* Port ANX78xx Pinebook / Teres LCD panel driver from 5.6-rc1
* Move Teres U-boot to 2020.01 ... it boots with enabled screen now.
* U-boot 2020 needs some extra Pyton utils when packing sunxi bootloader. Adding to native and Docker build dependencies.
* Add Pinebook lid wakeup
* python3-dev is also needed dependency
* [sunxi] allow pcm5102a codec module to be built
for sunxi-current and sunx-dev kernels.
Fixes#1798
* [sunxi] build pcm5102a and pcm51xx_(i2s|spi) modules by default
on sunxi-current and sunxi-dev kernels.
* Added ALSA configuration bits for rk3288 HDMI and SPDIF to allow
pulseaudio show proper sound device/profile/mapping names instead of
just "Built-in Audio" for all of them
* Added ALSA device description in asound.conf to provide correct labels for PulseAudio for RK3288 devices when SPDIF and DW-I2S-HDMI simple audio cards are exposed
Removed unnecessary ALSA configuration files previously added from rockchip.conf
* Fixed cpu operating points tables and raised a bit (+5°C) cooling for non-critical temperatures for xt-q8l-v10 in dev and next kernel flavours
* Fixed again cpu opp table
* Removed whole cpu opp table and retouch only necessary operating points
* Enabled gpiomem driver for xt-q8l-v10 in next kernel flavour
* Added debounce delay and card detect gpio pins for sdmmc card holder for xt-q8l-v10 board
* Added card-detect and debounce delay for sdmmc for xt-q8l-v10 board in next kernel flavour too
* Fixed missing comment in xt-q8l-v10 device tree patch
* Added gpiomem to xt-q8l-v10 board for dev kernel
* Fixed FAN53555/Silergy patches to accomodate changes in u-boot v2019.04
* Changed property property flags for USB regulators in u-boot and kernel: kernel is now informed that bootloader is going to turn the USB power on
* Fixed indentation in rk3288-xt-q8l-v10.dts, raised debounce delay to sdmmc, added vbus-supply to USB host, removed some unneeded properties
* Added working DDR52 mode for eMMC on xt-q8l-v10
* Removed regulator-off-in-suspend for some xt-q8l-v10 regulators due to changed in act8865.c driver which causes the regulators to be misconfigured
* Adjusted targets for xt-q8l-v10 (provides bionic desktop + buster server)
* Removed all regular-state-mem nodes in xt-q8l-v10 device tree because the change in act8865.c affects also non-off entries
* Brought xt-q8l-v10 device tree from rockchip-current to rockchip-dev
Adds k5.5 audio pipeline dts entries, adds audio to Renegade, cleans up some dts mess in renegade
- Note: PulseAudio seems to need to toggle a couple times before audio will play. That is not addressed in this patch.
* Add exceptions to support native Ubuntu 20.04 building, fix small bug related to SD card write verification.
* Improve first install steps by installing Dialog and lsb_release first. This left out since we moved host install after we choose what we will do ... dialog is essential for this. Second we don't wait properly for APT manager to finish the process. Fixed with this commit
* Suppress output
* Update OdroidXU4 dev config & patches
* Attach Meson64 to mainline with a bunch of patches. Tested, but need further work.
* Enable DVFS on N2 which sometimes works, sometime doesn't, cleanup
* Enable beta targets for Meson64 kernel family
* Bump with version
* Fix cpufreq (dynamic frequency scaling) for mvebu-current. Also move disabled patches in extra folder for better usability
* Move unlock-atheros-reg patch to disabled
* Accidentally deleted a patch instead of moving it to disabled. Restore it
* Survived standard stress testing + one night of normal operation (Helios4)
* Wireguard: bump tag to most recent since it breaks building on 5.4.y
* Move rockchip current to 5.4.y
* Move sunxi current to 5.4.y
* Move meson64 to 5.4.y
* Move odroidxu4 to 5.4.y and enable "current" targets
* Enable missing target
this update of the previous patch (#1663) additionally fixes the following overlays:
sun5i-a13: i2c1..2, nand, pwm, spi2, uart0..3
sun4i-a10: can, i2c1..2, pwm, spdif-out, spi0..2
corrections re #1663:
sun7i-a20: fixed typo in pwm overlay in #1663
arch64-makefile now back in line with original patch
this update of the previous patch (#1663) additionally fixes the following overlays:
sun5i-a13: i2c1..2, nand, pwm, spi2, uart0..3
sun4i-a10: can, i2c1..2, pwm, spdif-out, spi0..2
corrections re #1663:
sun7i-a20: fixed typo in pwm overlay in #1663
arch64-makefile now back in line with original patch
some armbian dts overlays currently do not work since pinctrl names have not been
adapted to renaming in 5.0 and 5.2.
this patch modifies the following overlays:
sun50i-h5: cir, spdif-out
sun8i-h3: cir, spdif-out
sun7i-a20: i2c1..4, mmc2, pwm, spdif-out, spi0..2, spi-add-cs1, uart4..7
sun5i-a13: uart0
sun4i-a10: spdif-out
some armbian dts overlays currently do not work since pinctrl names have not been
adapted to renaming in 5.0 and 5.2.
this patch modifies the following overlays:
sun50i-h5: cir, spdif-out
sun8i-h3: cir, spdif-out
sun7i-a20: i2c1..4, mmc2, pwm, spdif-out, spi0..2, spi-add-cs1, uart4..7
sun5i-a13: uart0
sun4i-a10: spdif-out
* Sunvell R69: cpu voltage regulator (re-)added - dram clock reduced.
CPU regulator (re-)added to u-boot and kernel dts - the box will not boot without it.
Dram clock reduced in defconfig to increase stability.
[AR-85]
* Updated rockchip64-dev to u-boot v2019.10 and BL31 v1.30 (rk3399 boards)
* Updated rk3399 to u-boot v2019.10 and BL31 v1.30
* Revert changes to renegade u-boot patches
* Moved renegade u-boot patches into board dir
* Added debug info for RockPro64 and switched sdmmc to fifo-mode
* Disabled regulators in SPL for RockPro64
* Re-enabled sd vcc regulator in SPL for RockPro64
* Some device tree and config changes for OrangePi RK3399
* Fixed Rock Pi 4A's $BOOTCONFIG
* Let some boards use mainline atf instead of the one in rkbin
For example, roc-rk3399-pc can just boot the kernel using the
mainline atf.
* Add roc-rk3399-pc
* Fixed reset in mainline ATF
* Attached ATF version to v2.2 tag
* WIP: sdmmc fifo-mode in SPL only
* Renamed source config files
* Reverted changes to rockchip64 sources config
* Reverted patch moves
* Add missing trust.ini patch to rk3399 u-boot
* Reinstated tpl/spl patches in rk3399 family
* Added $RKBIN_DIR prefix in rk3399 sources
* Add demonstration of boards bootloader assignment in rk3399
AR-1 - Adding support category for distributions
AR-4 - Remove Allwinner legacy
AR-5 - Drop Udoo family and move Udoo board into newly created imx6 family
AR-9 - Rename sunxi-next to sunxi-legacy
AR-10 - Rename sunxi-dev to sunxi-current
AR-11 - Adding Radxa Rockpi S support
AR-13 - Rename rockchip64-default to rockchip64-legacy
AR-14 - Add rockchip64-current as mainline source
AR-15 - Drop Rockchip 4.19.y NEXT, current become 5.3.y
AR-16 - Rename RK3399 default to legacy
AR-17 - Rename Odroid XU4 next and default to legacy 4.14.y, add DEV 5.4.y
AR-18 - Add Odroid N2 current mainline
AR-19 - Move Odroid C1 to meson family
AR-20 - Rename mvebu64-default to mvebu64-legacy
AR-21 - Rename mvebu-default to mvebu-legacy
AR-22 - Rename mvebu-next to mvebu-current
AR-23 - Drop meson64 default and next, current becomes former DEV 5.3.y
AR-24 - Drop cubox family and move Cubox/Hummingboard boards under imx6
AR-26 - Adjust motd
AR-27 - Enabling distribution release status
AR-28 - Added new GCC compilers
AR-29 - Implementing Ubuntu Eoan
AR-30 - Add desktop packages per board or family
AR-31 - Remove (Ubuntu/Debian) distribution name from image filename
AR-32 - Move arch configs from configuration.sh to separate arm64 and armhf config files
AR-33 - Revision numbers for beta builds changed to day_in_the_year
AR-34 - Patches support linked patches
AR-35 - Break meson64 family into gxbb and gxl
AR-36 - Add Nanopineo2 Black
AR-38 - Upgrade option from old branches to new one via armbian-config
AR-41 - Show full timezone info
AR-43 - Merge Odroid N2 to meson64
AR-44 - Enable FORCE_BOOTSCRIPT_UPDATE for all builds
* Fix wifi
patch "board-h2plus-nanopi-duo-add-device.patch": increase post-power-on-delay-ms from 50ms to 200ms in wifi_pwrseq node in nanopi-duo dts [dev-branch].
Change in line with other XRADIO device trees (orange pi zero, sunvell).
See also Pull Request #1605.
* Fix xradio patch (dev-branch)
fix KConfig to 5.x - WLAN_VENDOR-flag set to "y" in line with other drivers - otherwise module not loaded.
* correct device name
change nodes "model" and "compatible" to correct device name (from "NanoPi Duo AIR" to "NanoPi Duo") [dev-branch]
Not functionally necessary, but more correct.
U-Boot already support device tree overlay. However, it requires the
base dtb to be compiled with __symbol__ support.
This commit added patches to compile dtb with required parameter.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* UPSTREAM: media: rc: rename RC_TYPE_* to RC_PROTO_* and RC_BIT_* to RC_PROTO_BIT_*
Realigned the source code to the RC_TYPE* / RC_BIT_* refactoring
* Restored the inclusion of the DVB-USB dib0700 driver
Adjust configuration, merge with general purpose armv7 Fedora kernel, remove deprecated patch, move coherent_pool and cma to boot script
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
atomic_pool_size can be controlled by kernel cmdline,
coherent_pool=nn[KMG] [ARM,KNL]
then use this parameter to replace the patch.
Signed-off-by: Zhang Ning <832666+zhangn1985@users.noreply.github.com>
* Initial commit for serial consoles rfc
* Board configuration cleanup + small tweaks
* Add serial gadget rename to dev kernel as well
* Cleanup, fixing permissions
* Cleanup board configs
due to modpost is used by dkms or out-of-tree kernel modules, eg mali
so add this tool to linux-header's postinst script
for #1552
Signed-off-by: Zhang Ning <832666+zhangn1985@users.noreply.github.com>
* Initial commit for FA ZeroPi.
* Tested for building.
* Adjust few bugs.
* Move to WIP since its not tested on hardware yet.
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Added initial support of MCIMX7SABRE board
MCIMX7SABRE is NXP iMX7d-based board with 1Gb RAM
2xGBE, 1xmPCIe
Change-Id: I62685a55de54fa6109bef2a8e2ee760d831ffa0e
* Added initial support of MCIMX7SABRE board
MCIMX7SABRE is NXP iMX7d-based board with 1Gb RAM
2xGBE, 1xmPCIe
Change-Id: I62685a55de54fa6109bef2a8e2ee760d831ffa0e
* Changed BOARDFAMILY from mx7dsabre to imx7d
Change-Id: Id351c9f6a8c907b415b804bfe11b86027278ed86
* Disabled MD driver for imx7d Kernel
MD driver does not work correctly on NXP-modified kernel
Change-Id: I58e8de6ee0b99282c452f594e22f6f7e1ff59ae0
* Introducing build-all-ng
* Implementing REBUILD_IMAGES='board1,board2,...' for rebuilding certain images only
* Add optimisations when building kernels - only cycle trough needed targets. Adding variable for defining whether an image is build, otherwise only BSP is made.
* repository manipulating RFC
* Add bianco deb file that is added by default if repository is clean
* Switch to gpg2 signing method, small bugfix
* Create subdir for debs and debs-beta
* Synaptic bugfix: installing indexing tools https://forum.armbian.com/topic/8021-orange-pi-one-synaptic-package-manager-search-very-slow/?do=findComment&comment=74918
* add all modules by default to Odroid N2, but leave them commented
* Bugfix: not making any builds when selecting kernel_only
* Remove EXTERNAL=yes ... move armbian-config and armbian-firmware into main compilation area, drop others since they are deprecated anyway. This will also enable multi threaded images making
* Move armbian.list to create_sources_list function. Replace NTP by Chrony. Remove armbian-firmware from PACKAGE_LIST and RockPi 4A (#1528)
* Replace NTP by chrony. Remove installion of outdated armbian-firmware from reposity.
* added RockPi 4A
* New format for board config
* Fix Bluetooth dependencies for minimal package - add rfkill to family related installs
* Moving networkd-dispatcher from minimal image
* Cubox-i: update default config
* Improving umount process
* Add purgesource feature
* Add FULL_DESKTOP to install few more applications on top of our desktop - notebooks should * rk3399 default: adjust patches and configuration
* Enable full desktop on most powerfull boards and notebooks
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Added ALSA configuration bits for rk3288 HDMI and SPDIF to allow
pulseaudio show proper sound device/profile/mapping names instead of
just "Built-in Audio" for all of them
* Added ALSA device description in asound.conf to provide correct labels for PulseAudio for RK3288 devices when SPDIF and DW-I2S-HDMI simple audio cards are exposed
Removed unnecessary ALSA configuration files previously added from rockchip.conf
* Fixed cpu operating points tables and raised a bit (+5°C) cooling for non-critical temperatures for xt-q8l-v10 in dev and next kernel flavours
* Fixed again cpu opp table
* Removed whole cpu opp table and retouch only necessary operating points
* Enabled gpiomem driver for xt-q8l-v10 in next kernel flavour
* Added debounce delay and card detect gpio pins for sdmmc card holder for xt-q8l-v10 board
* Added card-detect and debounce delay for sdmmc for xt-q8l-v10 board in next kernel flavour too
* Fixed missing comment in xt-q8l-v10 device tree patch
* Added gpiomem to xt-q8l-v10 board for dev kernel
* Fixed FAN53555/Silergy patches to accomodate changes in u-boot v2019.04
* Changed property property flags for USB regulators in u-boot and kernel: kernel is now informed that bootloader is going to turn the USB power on
* Removed assert-phy-reset-when-waking-up-in-rk3288-platform patch due to inclusion in mainline 5.2 kernel
Reenabled ARM-DTSI-rk3288-add-usbphy-reset patch to include USB PHY reset lines to all rk3288 devices
* Removed ARM-DTSI-rk3288-add-usbphy-reset.patch due to inclusion in mainline kernel 5.2
* Attached cubox-i to stock kernel. Tested. Sadly ZRAM has some issues, so it must ramain disabled
* more imx6 updates for cubox/udoo
* Enable HDMI on Cubox-i
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
1, format all patches from https://github.com/megous/linux
`git format-patch 79bf89b88a87f2ebf147f76d8c40183283b49b51...2a7cb228d29c3882c1414c10a44c5f3f59bfa44d`
and copy them to sunxi-next with prefix `0000-`
2, remove unnecessary patches, due to they are revert of upstream patches:
4d867e2bd64e674a3000b8e05fe47e8bb8175edda2888276ee
3, remove fail to apply and no use:
960ddd63a8
4, remove WireGuard patch:
1cd13b836c
5, remove meaningless patch:
f26e36379a
6, remove merged or included by megous/linux patches:
0112-mfd-axp20x-Add-supported-cells-for-AXP803.patch
board-bpi-m3-make-ethernet-working.patch
board-pine-h6-pine-h6-0025-phy-sun4i-usb-add-support-for-missing-USB-PHY-index.patch
7, remove stable release update patches.
ignored.
8, rebase sunxi-next/sunxi64-next to upstream linux-4.19.y
test result:
all patches applied, no error.
orangepipc/orangpioneplus build OK.
Signed-off-by: Zhang Ning <832666+zhangn1985@users.noreply.github.com>
In current kernels (both next and dev) this patch breaks cpufreq and all that depends on it (no dvfs means board overheating). Removing it makes cpufreq and dvfs work again.
* fix kernelcrash with config_of_overlay combined with isp1 camera driver,based on:
30a8401c2f
* add basic dtbo infrastucture
* set ov5647 (RPi cam rev 1.3) as default, imx219 (RPi cam V2.1) outputs a blurry green videostream at the moment
* maybe fix powering for camera
* adjust mainline dtbo patch to bsp kernel
* got you! little.. dtbo's are properly built and applied during boot.
* add imx219 overlay to switch between cameras & add ae/awb fix for ov 5647 from asus tinker repo
* patch imx219 up to 96396323fa
* bring back wireguard, otherwise igor gets grumpy :D
* fix camera status
* 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
seems like this patch headed upstream for rk3328-roc-cc:
https://patchwork.kernel.org/patch/10804863/
doesn't include the tx/rx delay changes in the original rock64 patch:
https://patchwork.kernel.org/patch/10178969/
My testing showed these changes help with a link down and reset that happens on heavy
exchanges, like streaming. Maybe we should sumbit upstream a patch that hadles this as well?
Interrupt pin of the Ethernet PHY is connected to GPIO. The PHY can be
configured to raise interrupt when it received WoL magic packet.
This patch use gpio-keys as wakeup source for Wake on LAN as currently
there is no way to use the GPIO directly under mvneta driver.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
The SoC provides several waking options sourced by different peripherals
to take the system out of power save modes. One of the options is Wake
on GPIO.
This patch implements missing function to support gpio as wakeup source
and properly route it to upper interrupt controller (Arm GIC).
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
previous version of the patch has slightly higher performance impact
compared to disk activity trigger.
This updated patch should have similar impact as disk activity trigger.
- 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.)
Note: by default Orange Pi Zero Plus2 H5 boards are missing part of their regulator
hardware circuit; as such the default regulator is limited to 1.1v.
Reworked assert-phy-reset-when-waking-up patch to fit into 4.19 kernel DWC2 USB driver
Adding usbphy reset lines patch for rk3288.dtsi in both rockchip next and dev kernels
Removed same reset lines from xt-q8l-v10 next and dev device trees
- Adds the specific shortname per ASUS to allow controlled enumeration of the onboard USB audio codec
- kernel 4.19 saw some rewriting of the naming code
* 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
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 ...
