* Introduce the `BOARD_MAINTAINER` in board config
Yes, we have documented the maintainers in `armbian/documentation`.
But it seem like that some of them don't maintain anymore.
Use a separated repos make us forget to update it.
So let's document here.
What's more, defining this make us easier to update `.github/CODEOWNERS`
* Set `BOARD_MAINTAINER` accroding to `armbian/documentation`
* Guess `BOARD_MAINTAINER`
Set he/she as board maintiner if he/she:
1. Create the board config
3. Commit at lease 3 times for the board config
3. Commit most for the board config
* Guess `BOARD_MAINTAINER`
Set he/she as board maintiner if he/she:
1. Create the board config
2. The only one to commit for the board config
* Set `BOARD_MAINTAINER` to empty for other boards
* AR-1712 fixing PR from wrong DB
* Fixing maintainers
Signed-off-by: Igor <igor@armbian.com>
* Add variable to missing ones
---------
Signed-off-by: Igor <igor@armbian.com>
Co-authored-by: Rafal-Hacus <68160861+Rafal-Hacus@users.noreply.github.com>
Co-authored-by: Igor <igor@armbian.com>
* [ rockchip64] second round config migration
Recommend all @armbian/boards-rockchip maintainers double check the resulting configurations, as stated in the PR the level of confusion in the family config logic likely means some boards have unnecessary extra stuff.
* Enable CONFIG_BPF_SYSCALL which might improve Docker support
* Adjust board names
* Move neo3 to previous bootloader too
* Disable 3d support on rock64
* Add plymouth-theme-armbian package
* Adjust all bootscripts to adapt plymouth
* Auto show logo accroding to BOOT_LOGO
* Enable plymouth detail mode when bootlogo=false
* Add a new board config var - HAS_VIDEO_OUTPUT
This var is used to indicate whether device has a HW video output.
If it's set to "no", we will disable kernel bootsplash, plymouth and BUILD_DESKTOP
* Rename package to be aligned with others
* Disable kernel bootloader, but keep the code for it
* Rather keep bootlogo in the kernel for a while, otherwise kernel upgrade will turn bootup into the darkness
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
Co-authored-by: Igor <igor@armbian.com>
* 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>
