> Based on AmazingFate's kernel DT and Kwiboo's `rk3568-2023.10`
Tested with a OrangePi 3B 4GB v1.1:
- SD-card boot
- eMMC boot
- SPI Flash boot
- chip is XMC `XM25QU128CWIQ`, not `W25Q256JWEIQ` listed in schematics
- PCIe/NVMe
- Ethernet has stable MAC
- can boot both edge (mainline) and legacy (vendor rk 5.10) kernels
- USB in uboot is untested
- UMS untested (I lost my A-to-A otg cable)
After we bumped u-boot to version v2022.10, a couple of boards
stopped booting because the CONFIG_SPL_STACK value used in our
u-boot config was too low for that SOC. This change drops explicit
CONFIG_SPL_STACK defination from the affected boards.
The boards confirmed to have the issues were Orange Pi 3 LTS and
NanoPi Neo Black2 but I suspect that NanoPi K1 plus is also affected
hence similar change is done for that as well
- using Kwiboo's `rk3568-2023.10` branch with BINMAN-handled blobs
- patches (defconfig unless indicated):
- boot usb first (rockchip-common)
- blink leds & keep red one one on preboot; reset SPI env once after deinfesting from Petitboot
- change usb_host0_xhci to otg (u-boot dtsi)
- enable DM_GADGET, UMS 🔥 and RockUSB
- **usage instructions**:
- build & burn image to SD card
- insert SD card into board
- **hold the recovery (RCY) button** and power on the board
- watch board boot
- **de-infest Petitboot**: use `armbian-install` to install bootloader to MTD
- if you don't, you'll need to hold the recovery button every boot
- optionally: use `armbian-install` to install OS to eMMC/NVMe/USB
- power-off board
- remove SD card (new u-boot always boots SD first!)
- boot into your newly de-infested machine
- boot order: USB, SD, MMC, NVME, SCSI
- de-infested machine can now boot (directly) from USB/SATA/NVMe, possibly via EFI:
- Armbian UEFI-arm64
- Fedora 38 aarch64
- HASSOS for ODROID-M1
- Talos arm64
- others...
- extra: new u-boot by Kwiboo (with GMAC patches) gives us stable MAC address
- although it is based on cpuid#, doesn't match the HK sticker on the board
- run `fw_setenv ethaddr XX:XX:XX:XX:XX:XX` to change eth addr in SPI flash environment if needed
- `odroidm1`: update DDR/BL31 blobs (this depends on https://github.com/armbian/rkbin/pull/20)
Backport DTS/DTSI changes from linux-6.4.y to 6.1.y
Add meson64-reboot driver to all boards
Add board: ODROID N2L
Add uart_A uart_AO_B uart_B uart_C where appropriate
U-Boot v2023.07.02: ODROID N2/N2L/N2Plus/C4
Meson64-reboot driver: (source: tobetter)
While the current meson64-reboot driver is cleaner and doesn't
depend on modding other kernel sources, its functionality leaves
much to be desired. One example can be found in the ODROID C4.
Using the current driver, the board will not properly power off,
leaving the POWER LED still on. The new driver powers off the unit
completely.
Fan control: (ODROID N2L/N2PLus)
Added service and script for controlling the trip point.
fanctrl: arguments: 65 55 45 35 25 menu run
┌──┤ Fan Control ├──┐
│ │
│ 6) 65°C │
│ 5) 55°C │
│ 4) 45°C │
│ 3) 35°C │
│ 2) 25°C │
│ E) Exit .. │
│ │
│ │
│ <Ok> │
│ │
└───────────────────┘
NOTES: (N2L/HC4): I do not own the units so I can't run tests.
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Removed WIP status
Added CONFIG_R8169=m to defconfig(s) (eth support)
Modified and added additional patches (linux 6.1 / 6.4)
U-Boot v2023.07.2 (dropped v2022.10)
Upstream BT FW (rtl8822cs) is now shared between CM4IO and M2s
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
- `2023.04` fails during USB init, thus using 23.01 (23.07 untested)
- `blobless` with newer 2.8.5 ATF
- the previous problems with PCIe are _not_ totally solved by this
- meko: don't use Radxa's Rock-5A u-boot anymore, switch to rockchip vendor next-dev branch
- meko: my own (horrible) patches for MAC address stability / defconfig
- meko: cherry picked a few patches for getting rid of BL32/read Bl31 from env and other fixes from Radxa
- meko: add OTP node to 3588 dtsi (so we don't need kern-dtb in ITS for working OTP)
- meko: refactor common code across 3 (soon to be 4) board files into vendor conf and hooks
- meko: bump DDR/BL31 blobs for all Meko boards
* Add support for Recore
Signed-off-by: Elias Bakken <elias@iagent.no>
* Add board maintainter to boad config
Signed-off-by: Elias Bakken <elias@iagent.no>
---------
Signed-off-by: Elias Bakken <elias@iagent.no>
- those were clearly/unfortunately meant to be applied "after" the common patches, so add a `zzz-` prefix
- how did this _ever_ work before? unclear...
- `sunxi_common`: don't overwrite `BOOTPATCHDIR` if it is set by the board (default, but do not overwrite)
- hammer `allwinner-h616-GPU-enable-hack.patch`
- symptoms:
- no video display in u-boot
- can't boot from SD (but does from eMMC)
- this has proven to solve nothing, but is still neat
- real problem is probably the FIP?
- have absolutely no idea if this works. there's also some other `armv5` variants to try if this does not.
- XU4's CPU is Exynos5422 ARM Cortex-A15 which should be armv7-a indeed, so why not?
- i.MX 6 series is ARM Cortex-A9 or Cortex-A7, which should be armv7-a indeed, so why not?
- ARMADA A388 is 32-bit Cortex A9, which should be armv7-a indeed, so why not?
- sharing most UEFI code, will replace the `virtual` one soon
- x86: patch uboot defconfig to use the `q35` machine type, not `i440fx`
- separate x86 bootscript, due to non-uInitrd-ness of it
- hack ramdisk load address both in u-boot source and bootscript
- use 32-bit u-boot, not 64-bit
- grub: introduce `UEFI_GRUB=skip`, does not deploy GRUB (but does the kernel packages, etc)
- auto-enable qcow2 output for these
- works with both distro's and Armbian's kernels
U-boot-rockchip64. No code changes. Original patch applied and new patch generated then mbox tweaked to retain relevant details. Prevents patching errors in armbian-next.
* Fixed u-boot v2022.07 compilation for Helios64
* Move Helios64 back from EOS to community supported as images can be assembled
Co-authored-by: Igor <igor@armbian.com>
- notes in the board file about the RAM issues (tested, confirmed working blob change of #4383 by @pinhaozhang working with u-boot 21.07; `blobless` also works with ATF v2.7 on my known-good-RAM boards)
- tinkerboard-2: add full firmware, for the rtl8822ce PCIe Wifi default card in the tb2 as shipped by ASUS
- tinkerboard-2: uboot: rename `TARGET_TINKER-2_RK3399` to `TARGET_TINKER2_RK3399` to avoid warnings all over
- tinkerboard-2: slower but working Tinkerboard 2S eMMC (HS400+ES to HS200)
- both for u-boot and kernel.
- should not affect 2, only 2S
* `meson64`: `6.0`: g12a and g12b pinmux patches from Radxa
* u-boot: `radxa-zero2`: Radxa's patches for the Zero2 on `v2022.10`
* u-boot: `radxa-zero2`: use `v2022.10` plus Radxa's patches
* `meson64` u-boot v2022.10: change `BOOT_TARGET_DEVICES` to try to boot USB, NVME and SCSI before SD, MMC, PXE, DHCP
* `radxa-zero`: include v2022.10 standard patches (eg: boot from USB first)
* Move all legacy u-boot patches under one general legacy folder
* Move 32b Rockchip under 2022.04 and legacy for Miqi
Tested
* Move Rock 3A patch dir under legacy
* Move / merge meson64 patch folder into v2022.07
Merge 2022.04 (mainly Rockchip 32) into 2022.07, tested
* Remove not needed patch
* Add last kernel version to config
* `odroidm1`.wip: hk's `legacy`= 4.19 and `edge`= mainline+tobetter's 5.19 rebased; *requires* `skip_spiboot=true`
- @TODO: family/etc naming is terrible with vendor kernels. Sorry. Fight over it and let me know?
- @TODO: config is very probably incomplete.
- new `boot-rockchip64-vendor.cmd`:
- does not use fixed load_addr, instead use ramdisk_addr_r for everything
- load kernel and initrd as late as possible
- look for overlays twice:
- once: with prefix and folder
- twice: without prefix, nor folder; helps with vendor provided overlays like hk's and tobetter's
- wip: edge: tobetter's patchset rebased against 5.19.3
- wip: edge: bump to tobetter's 5.19
- legacy: .config `CONFIG_ARM64_VA_BITS_48=y`
- wip m1: update legacy config from odroid
- odroidm1: container/bpf stuff in legacy config
* Update configs and enable beta build target
* Adjust current kernel
* Update targets
* Remove everything but EDGE kernel
* Cleanup
* Fix
Co-authored-by: Ricardo Pardini <ricardo@pardini.net>
* rock-5b: add initial raxda rock-5b .wip (by @amazingfate); vendor u-boot & kernel
- .wip board
- using BOARDFAMILY `rk35xx`, which was for rock-3a
- patch by @piter75 uboot for working 'source' command so boot.scr can be used, and not extlinux
- .config: hammer CONFIG_JOYSTICK_XPAD & CONFIG_JOYSTICK_PSXPAD_SPI
- rock5 add kernel optiions by @lanefu
- disable CONFIG_LOCALVERSION_AUTO otherwise packaging goes insane
- make its kernel is own LINUXFAMILY to as to not mess up rock-3a
- CONFIG_VT=y & SKIP_BOOTSPLASH="yes"
* Add separate family for rock 5b - rockchip-rk3588
Co-authored-by: amazingfate <liujianfeng1994@gmail.com>
Co-authored-by: root <catalinii@yahoo.com>
* tf-a sources use mrvl_flash rather than 'all' target
* add armada 8k ethernet and SFP cages for macchiatobin use
* u-boot configuration for mcbin
* fix bootscript for u-boot variables
* separate ebin and mcbin with if statements
* add a8k PCIe and CPUFreq drivers for macchiatobin
* alias defined in patch 0007 is part of armada-372x.dtsi, so unnecessary in 37xx
* u-boot patch to dts shouldn't disable emmc or overwrite sdhci1
* update u-boot
* Rockchip64 Linux-5.10y - drivers for Motorcomm YT8531
renamed the previous "net-phy-Add-driver-for-Motorcomm-YT85xx-PHYs.patch" to "net-phy-Add-driver-for-Motorcomm-1-YT85xx-PHYs.patch" to fix patch order and added a new patch "net-phy-Add-driver-for-Motorcomm-2-YT8531-PHYs.patch"
The new YT8531 patch is sourced from from Lean's OpenWrt source rockchip/patches-5.10/601-net-phy-Add-driver-for-Motorcomm-YT8531-PHYs.patch.
It is intended to extend a patch identical to Armbian's "net-phy-Add-driver-for-Motorcomm-YT85xx-PHYs.patch" and is used without alteration.
* Add new board OrangePi R1 LTS (rk3328)
Includes uBoot and support for Linux-5.10y
* Rockchip64 Linux-5.15y drivers for YT8531 and other Motorcomm chips
YT8010, YT8510, YT8511, YT8512, YT8521. The driver patch set is sourced from Xunlong-OrangePi OpenWRT and is used as is, with only a name and makefile change.
A single patch set uses the same underlying source code as the Armbian Linux-5.10y set, but uses inbuilt logic to apply tweaks that depend on the Linux kernel version.
The patch is renamed similarly to the 5.10 patch set, net-phy-Add-driver-for-Motorcomm-T85xx+PHYs.patch to imply code base continuity with the previous similar Armbian patch sets.
* Rockchip64 Linux-5.15y support for Orange Pi R1 Plus LTS
Includes DTS and makefile changes. A driver for net phy YT8531C is in a separate commit
* change orangepi-r1plus-lts.csc to orangepi-r1plus-lts.conf
board is now supported
* - add patch also to 5.16.y
- fix wrong patch permission
* Fix Makefile patch
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
Radxa Zero 2 is a small form factor SBC based on the Amlogic A311D
chipset that ships in a number of eMMC configurations:
- Amlogic A311D (Quad A73 + Dual A53) CPU
- 4GB LPDDR4 RAM
- 32/64/128GB eMMC
- Mali G52-MP4 GPU
- HDMI 2.1 output (micro)
- BCM4345 WiFi (2.4/5GHz a/b/g/n/ac) and BT 5.0
- 1x USB 2.0 port - Type C (OTG)
- 1x USB 3.0 port - Type C (Host)
- 1x micro SD Card slot
- 40 Pin GPIO header
Signed-off-by: Yuntian Zhang <yt@radxa.com>
* Bump Meson64 u-boot to 2022.01
Tested VIM boards
* Move Jethub related patches under common meson64 patch collection
* Move jethub patch to per board and remove unneded settings
* Sync kernel config with radxa and remove packaging patch
* Merge the rockchip64 legacy config as well
* Lower priority of EFI partitioning against DOS partitioning which is used by Armbian
Co-authored-by: Catalin Toda <catalinii@yahoo.com>
* JetHome: Update u-boot patches: fix emmc work on JetHub D1
* JetHome: update kernel patches with last updates for JetHub devices.
* JetHome: Update Bluetooth init script to more stable start.
* Switched rockchip64 u-boot to v2021.07
* Switched OrangePi R1 Plus to include mainline's R2S device tree
* Added unsingned signed comparison patch from Paolo to fix rk3328 reboots
* Bugfix - Bananapi PRO seems to work fine with latest u-boot
Done many reboots and it didn't break. The same has to be tested with other A20 boards
* Set Allwinner 32bit hw to most recent u-boot 2021.07
* Let's move all to 2021.07 and test ...
* meson64: bump u-boot to 2021.07, rework patches
- as always based on chewitt's tree, with differences:
- squashed versions of HC4+SATA, Radxa Zero, DT tree sync patches
- so that DTB/config/code changes related to the same feature/board are grouped
- removed documentation changes and Makefile reordering patches
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* meson64: ODROID HC4/N2: simplify/remove board vs family hacks; better SPI support
- thanks to mainline 2021.07 u-boot and it's HC4 config we can remove the conditionals
- boards now define the u-boot vars instead of conditionals in family
- on the HC4, build u-boot twice: one for SD (old C4 config) and one for HC4 (new SATA/SPI config)
- reason is that the HC4 version does not work very well unless it is actually booted from SPI
- meson64_common: don't override UBOOT_TARGET_MAP if board-defined
- but the default UBOOT_TARGET_MAP is still defined if the board didn't
- (sneakily) add lm-sensors fancontrol to the HC4's board packages
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* Add support for Radxa Zero
u-boot: new patch based on v2021.04
kernel: use patches sent to kernel list by chewitt
Tested with minimal build and cinnamon desktop:
- SD/eMMC, ok
- USB3, works in USB 2 mode
- HDMI, ok
- WiFi/BT, ok
Signed-off-by: Jack Ma <jack@radxa.com>
* Add build targets
* Cleanup and set min speed to 666000
* Change to WIP target
Support status undetermined
Co-authored-by: Jack Ma <jack@radxa.com>
* [ Rockchip64 ] Add Tinker Board 2
Using Mainline ATF/U-boot/Kernel
What works:
- USB (NOT TYPE C)
- PCIe
- LED's
- Ethernet
- HDMI
TODO:
- Type-C (fusb302 stuff)
- Type-C DP
- Regulators for big cores and GPU (sitting at default values now, no DVFS)
- Formware/driver for RTL8822CE
U-boot spits out some trash right after handing off control from SPL to U-Boot,
but doesn't impact boot. Needs looked at.
* [ rockchip64 ] remove unrelated changes to 369ab2decdc5a3c49973d8eeb783c95558dcc41a
* [ rockchip64 ] fix merge mess from symlinks step 1
* [ rockchip64 ] fix merge mess from symlinks step 2
* [ rockchip64 ] fix merge mess from symlinks step 3
* [ rockchip64 ] add asus driver for FAN53200 regulator
* Rename tinkerboard.conf to tinkerboard.wip
set as WIP for merge to trunk. Not ready for images just yet.
* revert rename to wip
wrong tinkerboard
* Rename tinkerboard-2.conf to tinkerboard-2.wip
prepare for merge to trunk. Not ready for images
* Tinker Board 2 GPU and Type-C
Support USB3 over type-C connector. display Port is still non-functional, framework in device tree however
Enable GPU
* Tinkerboard 2 DTS tweaks
Added this round:
Type-C DP now works
thermal sensors enabled (oops)
* Tinker Board 2 update config
-Adds wifi support for the RTL8822
* Updated kernel/u-boot for MCIMX7SABRE board
Supporing 'current' and 'legacy' branches for MCIMX7SABRE board
current branch:
u-boot: imx_v2020.04_5.4.70_2.3.0
kernel: imx_5.4.70_2.3.0
legacy branch:
u-boot: imx_v2018.03_4.14.98_2.0.0_ga
kernel: imx_4.14.98_2.0.0_ga
* Update kernel config with few additional options like zram, bonding, ... just a few to keep minimum consistency over kernels.
* Fixed u-boot script and kernel config for i.MX7D
Fixed bug in u-boot script preventing to use armbianEnv.txt
Configured SDMA as module to fix loading SDMA firmware
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* remove obsolete and broken patch for pine64so u-boot
This prevents the image from being built.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
* sunxi: fix pine64so phy-mode and add yt8511 support
Pine A64-LTS board should have RGMII-TXID mode instead of RGMII-ID (the
Realtek PHY chip's RXID is sometimes broken).
In addition, new Pine A64-LTS v2 board will use YT8511 instead of
RTL8211E, which still works under RGMII-TXID mode.
Backport YT8511 driver and phy-mode change from linux-next.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
* Updated kernel/u-boot for MCIMX7SABRE board
Supporing 'current' and 'legacy' branches for MCIMX7SABRE board
current branch:
u-boot: imx_v2020.04_5.4.70_2.3.0
kernel: imx_5.4.70_2.3.0
legacy branch:
u-boot: imx_v2018.03_4.14.98_2.0.0_ga
kernel: imx_4.14.98_2.0.0_ga
* Update kernel config with few additional options like zram, bonding, ... just a few to keep minimum consistency over kernels.
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Remove unnecessary patch
- this patch works when compiling and installing manually.
- the dtb with the changes is taken from the kernel and not from u-boot, therefore this patch does not work.
* Add enable-audio-codec-bpim2ultra-kernel.patch
- Add patch to enable audio codec in bpi-m2-ultra with h3 compatible
- Built and tested on Armbian Buster with Kernel 5.11.x (edge)
* Bump imx6 edge to 5.12.y
* Bump odroid xu4 edge to 5.12.y
* Bump Jetson nano edge to 5.12.y
* WIP: Bump sunxi to 5.12.y
- create a copy of patches and make a new link
- wireless patches needs adjutement to 5.12
- some patches are still failing
* Adjust wireless patches to build on 5.12.y
* Remove template wireless patch
* Move Espressobin edge to 5.12.y
* Bump mvebu to 5.12
- patch 92-mvebu-gpio-remove-hardcoded-timer-assignment.patch was disabled @heisath
- adjusted wireless driver for 8723ds
* Adjust sunxi / sunxi64 edge to compile
* Fix kernel config for Jetson nano edge
* bump meson64 to 5.12.y
* bump rockchip edge to 5.12.y
* Bump rockchip64 to 5.12.y
* Bump rk322x edge to 5.12.y
@paolosabatino
* Cleanup im6, re-add 5.10.y patches since one is missing in 5.12.y
* Update odroidxu4 edge links
* rk322x: moved rk322x-edge to kernel 5.12, fix overlay compilation, retouched included kernel modules
* Cleanup: remove deprecated config
Co-authored-by: Paolo Sabatino <paolo.sabatino@gmail.com>
* Remove unnecessary patch
- this patch works when compiling and installing manually.
- the dtb with the changes is taken from the kernel and not from u-boot, therefore this patch does not work.
* Add enable-sound-pinecube-kernel.patch
- Add patch to enable audio codec in pinecube with v3s compatible
- Built and tested on Armbian Buster with Kernel 5.11.x (edge)
There are already emmc nodes in rk3288-tinker-s.dts, adding these nodes
to rk3288-tinker.dtsi will cause emmc busy loop on original Tinkerboard.
Signed-off-by: Jack Chen <redchenjs@live.com>
* fix SPL not booting due to signed/unsigned integer comparison
* gpio7 now uses dm-pre-reloc to correctly compile TPL
* adjusted minor thing is defconfig, more room for stacks
* includes patch for efuse for next v2021.04
- Enabled nfc on rk322x-dev and disable on rk322x-current (need further development)
- Tidied up rk322x-current device tree
- enabled nfc rockchip driver enabled in rk322x-dev kernel config
- Enabled EHCI controller in u-boot (added patch for inno-phy, device tree and config bits), better device detection for dwc2 usb otg port
- Removed SPL_FIT_GENERATOR from u-boot configuration, fixed .its file to use binman
- fixed rk322x its file (now includes dtb), reverted u-boot to v2020.10 and changed dev_* into log_debug() calls
* Adjust the RK808 buck step to improve stability
* Adjust vdd_log and enable vdd_center init voltage
For some reason, regulator-init-microvolt property under PMIC does not applied. Set the voltage on board file.
* Explicitly set vdd_log voltage for NanoPi M4V2 - possibly fix stability issues
* Regulator tweaks for NanoPi M4V2
* Add vdd_log to kernel and switch vdd_center back to 900mV
* Switch vdd_center to 0.95
* Make rk80x bucks voltage steps shorter to make the NanoPi M4V2 stable
* Tweak u-boot config for NanoPi M4V2
* Made the rk808 voltage steps configurable and configured 50mV for NanoPi M4V2
* Switched rockchip64/rk3399 to u-boot v2020.10
* Some tweaks for SPI booting on ROCK Pi 4 in u-boot v2020.10
* Adjusted NanoPi M4V2 config for u-boot v2020.10
* Disabled PREBOOT for RockPro64 in u-boot v2020.10
It breaks boot during fdt loading
* Fix issues with booting from SPI flash for RockPro64
* Moved NanoPi R4S patches to board specific folder
* Upgrade Meson64 u-boot to 2020.10
Tested on C1,C2 and C4
* Remove accidentaly added patch
* Remove patches that are not needed anymore and restore / adjust the one that is still needed for Lepotato
* sunxi: kernel: current/dev: enable sun6i-csi and disable LL debug on UART0
The former is useful on some boards, e.g. PineCube.
The latter blocks boards that do not utilize UART0 from booting.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
* sunxi: add new family sun8i-v3s
This family is intended for boards with V3/V3s/S3/S3L chips and low
DRAM capacity.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
* sunxi: add PineCube board
This board features Sochip S3 SoC (Allwinner V3 die + co-packaged 128MiB
DRAM), and an OmniVision OV5640 camera is shipped with the board.
Add support for it. It could be used as an IP camera then.
Kernel support is only added to current/dev branch, with dev just using
mainline-merged DT and current using backported DT from 5.10-rc.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
* sunxi: kernel: current/dev: add V3s OHCI/EHCI nodes
These are needed for USB host on V3s boards to work.
Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
* Move changed rockpis changed patch to board specific and add original one to z28pro
* Delete the patch unneeded for ROCK Pi S
Co-authored-by: Piotr Szczepanik <piter75@gmail.com>
* Enable ums and maskrom u-boot recovery button
* Configure USB MUX before starting download mode
* Blink system status led to notify user the download mode
* Move HDD power staggering to board function
* Configurable u-boot recovery for rockchip64 (ums,rockusb,fastboot,maskrom)
* Switch RockPro64 to configurable u-boot recovery
* Added a hook for board to prepare download mode
* Some fixes to mmc device detection
* Use dedicated led functions and fixups
* Switched RockPro64 to mainline u-boot
* Enabled rockusb and ums for RockPro64 in mainline u-boot
* Switched RockPro64 u-boot to TPL/SPL/BLOB scenario
* Enabled advanced recovery button support for RockPro64
* Disabled SDR104 mode for RockPro64 in legacy
The helios64 devicetree was submitted for inclusion in the mainline kernel.
The name used there is rk3399-kobol-helios64, so use the same here
for consistency, to be easily able to boot a mainline kernel without
changing the U-Boot environment and simplify further development.
* Switched Pinebook Pro to mainline u-boot
* Some Pinebook Pro mainline u-boot tweaks
(based on https://github.com/pcm720/u-boot-build-scripts)
* Removed Pinebook Pro legacy u-boot support
- Chanaged default x.org configuration to disable glamor
- Reintroduce patch to use DRM cursor plane as overlay in rk322x-current and -dev
- Updated wifi patches for kernel 5.8.10
- Bumped rk322x to u-boot v2020.07, removed reserved zones from device trees
- Updated OPTEE to v3.10, using ddrbin v1.10
- Bumped rk322x-current to kernel 5.8.y
- Imported new patches from knaerzche's LibreELEC fork for rk322x-dev (kernel 5.8.y)
- Adjusted existing patches to match changes, updated rk322x-dev kernel config file
- Add default modprobe conf file for esp8089 to force the crystal frequency to 40Mhz for rk322x targets
- Removed ssv6051 firmware packages to move to armbian-firmware repository
- Switching ssv6051-wifi.cfg to /lib/firmware for rk322x-legacy
- Removed P2P interface for esp8089 driver for rk322x-legacy
- Optimized ssv6051 performance: kernel module gains -Os flag, disabled p2p interface, enabled HW crypto for CCMP cipher
- Enabled remote control interface, IR GPIO kernel module and HDMI CEC modules
* Helios64: rework vdd_log and vdd_center
* helios64: Use rockchip binaries for legacy and current branch
Fully open source bootloader only on dev branch
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* rework vdd_log and vdd_center patches
* Supress systemd service warning
* helios64: u-boot: staggered HDD power up
Set the delay to 10s in between turning on the next HDD power rails.
Remove the delay property from kernel device tree, let it only apply to
u-boot
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* helios64: fault LED as kernel panic indicator
also sync, u-boot dts
* helios64: fix hwmon udev rules
Legacy kernel (LK 4.4) has different class/naming on SoC Temp sensor.
Also fix typo on current/dev udev rules.
* Add initial Helios64 configuration
Add ethernet udev rules
Added disable auto power on script during shutdown
Configure ALSA to output audio to (DisplayPort) USB type-C
armbian-firstrun: exclude helios64 from generating fixed_mac
Each network interface on Helios64 already assigned to unique MAC
address in factory. Assigning Network Manager with cloned MAC is not
needed.
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* u-boot: rk3399: Add Helios64
Use rockchip propriettary loader
* kernel: rk3399-legacy: Update r8152 to support 2.5GbE USB RTL8156
Required for Helios64
* kernel: rk3399-legacy: update Rockchip PCIe driver
Port changes by ayufan on rockchip64.
* kernel: rk3399-legacy: Add support for Helios64
Add Helios64 device tree.
Enable missing driver/kernel module.
Auto load lm75 modules
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* kernel: rk3399-legacy: rework roc-rk3399-pc patch
the patch broken due to additional line added by helios64 on
arch/arm64/boot/dts/rockchip/Makefile
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* kernel: rk3399-legacy: update Rockchip PCIe driver
Backport bugfix from mainline
refer to
https://patchwork.kernel.org/patch/11561979/
and
https://patchwork.kernel.org/patch/11561977/
Signed-off-by: Aditya Prayoga <aditya@kobol.io>
* kernel: rockchip64-current: Add support for Helios64
Add Helios64 device tree.
Enable missing driver/kernel module.
* config: helios64: use mainline ATF on current branch
and u-boot TPL/SPL instead of Rockchip proprietary loader
* helios64: u-boot v2020.07 update
* Add Helios64 target
* kernel: rk3399-legacy: update Rockchip PCIe driver
Removed unrelated changes from porting ayufan fixes
Signed-off-by: Piotr Szczepanik <piter75@gmail.com>
* helios64: make use of PACKAGE_LIST* variables
Co-authored-by: Piotr Szczepanik <piter75@gmail.com>
* Add initial support for Odroid N2+
* Update C4 config and test booting
* Updates to C4, N2, N2+
- merge C4 and N2 legacy under meson64, same u-boot
- upgrade legacy kernel to meed DTB from mainline
- merge N2 and N2+, add a hack to display + in motd when N2+ is detected
- shortly spin N2 fan at startup
- merged N2 mainline and legacy boot script
- add upstream patches
* One of the regulators were breaking booting of Odroid N2
Co-authored-by: Werner <EvilOlaf@users.noreply.github.com>
* 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
* 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
odroidc1 can fail to boot probably depending
on features of the ext4 rootfs that is created
during the build process
serial log error:
Loading file "/boot/uInitrd" from mmc device 0:1 xxa1
invalid extent block
since there is no support for that board in upstream u-boot
backport the patch from
upstream commit:b5bbac1a9b07016602559ff483df265fef6c1f83
see also [1]
[1] https://lists.denx.de/pipermail/u-boot/2014-January/170802.html
Signed-off-by: Dirk Neukirchen <plntyk.arm@plntyk.name>
* 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>
* Disable DE2 in u-boot to improve EDID detection
* Remove deprecated patches
* Define BOOTBRANCH in top level
Signed-off-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* 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.
* 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
* 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
* 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
* 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>
The eMMC must have been forgotten when the device tree for the NanoPi Neo Air was being added to mainline u-boot, which results in the device being unable to boot when installed to the internal eMMC using the nand-sata-install utility.
