* Bump sunxi kernels
* sunxi-5.19: Remove pre-applied patch, adapt for series
* sunxi-5.15: Adapt patches to the series, remove previously applied
* Bump it again
Co-authored-by: The-going <48602507+The-going@users.noreply.github.com>
G12/GXL boards with memory of 1GB or lower are unable to boot because the CMA memory pool is set to high. Leaving CMA at the default and providing an overlay for those who need or want the CMA higher, makes more sense than not supporting all possible memory options provided by said SoC(s).
* meson: bump version
bump edge to thirdparty linux-5.18-rc7
bump current to linux-5.15
change legacy back to LTS linux-5.10
* Upgrade kernel config
* meson: edge and current: Enable NTFS3 driver
* Solve compatibility issues for some of wifi patches, disable those that needs more work
* Fix 8812au
* Update to re-enable RTL88x2CS driver for 5.19.2+
* Add 8723ds and rename others
* Following naming convention
* Name
* Adjust UWE5622 for 5.19.2
* Update UWE5622 patch for sunxi
* Enable last one
* Fixes for 8723DU
Co-authored-by: Vyacheslav Bocharov <adeep@lexina.in>
* sunxi-5.19: Initial state for megous patches
* Add the ability to do 5.19
* Move to 5.19
- tested both
- removed broken Opi Zero xradio driver https://armbian.atlassian.net/browse/AR-1280
* sunxi-5.19: fix tag for switch
* sunxi-5.19: Initial state for armbian patches
* sunxi-5.19: Add armbian patches to series.conf file
* sanxi-5.19: Add other 2 patches
* sunxi-5.19: Limit to use the 'wireless/xradio' module
Limit the kernel version to less than 5.19 to use
the 'wireless/xradio' module
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* meson64-edge/5.19: use `tag:v5.19-rc2`, meson64 kernel config and kernel patches, by @adeepv
* meson64-edge/5.19: we don't need `CONFIG_ARCH_ROCKCHIP=y` for meson64, right?
* meson64-edge/5.19: remove `meson_drv_shutdown` revert patch, instead `CONFIG_DRM_MESON=y` and its dependencies in .config
- this allows other meson64's to shutdown properly, while allowing the N2(+) to reboot without kernel-side hangs
* meson64-edge/5.19: odroidn2(+): remove SD UHS modes patch for ODROID N2(+)
- it works when cold-booted
- but changes voltage to enable
- when rebooted, voltage persists and uboot can't read the SD anymore
- adding the "odroid,reboot" driver+dt that is supposed to fix this, doesn't
- so for now remove it
* meson64-edge/5.19: odroidn2(+): add dumb gpio fan at 30 celsius
- backport from rework in 5.10
* meson64-edge/5.19: odroidhc4: bring back `fan1_input` by adding fan details to DT
- yeah, I know; the cooling map is right there too, so empty, poor thing. for later.
* meson64-edge/5.19: bump to 5.19-rc3
* meson64-edge/5.19: radxa-zero: add patch to remove UHS mode so `wifi` works
- sent by @pyavitz: https://raw.githubusercontent.com/pyavitz/debian-image-builder/feature/patches/amlogic/radxazero/wifi/001-arm64-dts-amlogic-radxa-zero-sdio-card-speed.patch
- tested by @lanefu
* meson64-edge/5.19: bump to 5.19-rc4
* meson64-edge/5.19: bump to 5.19-rc5
* meson64-edge/5.19: bump to 5.19-rc7
* meson64-edge/5.19: bump to 5.19.y branch, which is 5.19.0 right now
* Add kernel config - tested on Odroid N2+
Co-authored-by: Vyacheslav Bocharov <adeep@lexina.in>
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
- uefi-arm64-edge/5.19: add patch for ACPI enablement of PHYT0004 onboard network card
- reworked 5.10 version of patch to 5.19, trivial datatype change
- sent by Dragonbox/Pythium person via @lanefu
- uefi-(arm64|x86)-edge/5.19: split patch dir from x86, otherwise identical
* Skip applying fixes for touchscreen: goodix.
This device is not supported by armbian.
Patch fixes cannot be tested on real hardware.
* Bring the patch format to the form git-format-patch
for application by the `git am` command.
* This disables support for the RockPI-S "SDNAND" soldered on EMMC storage
Without it, SDNAND functions
There are no issues on boards that lack the EMMC storage option
In this case, the kernel probes the chip, quietly fails and continues without
creating the corresponding /dev/mmcblk* nodes
* This patch attempts to enable CPU operating points that are not defined.
The result is that the cpufreq-dt driver aborts when attempting to process these incompletely defined nodes.
The CPU ends up running at a constant clock rate, without cpufreq support.
Simply removing the patch restores proper cpufreq operation.
Note, however, that the CPU operating points are still overvolted for the newer RK3308B-S SOC.
See:
https://dl.radxa.com/rockpis/docs/sw/RK3308B-S&RK3308H-S_Software_Compatibility_Introduction_V1.0.0_20211016.pdf
* sunxi-5.18: add megous patches: tag: orange-pi-5.18-20220627-1924
* tools: mk_format_patch: ignore-matching-lines git version
* sunxi-5.18: re-extracted armbian patches after being applied to 5.18.8
* sunxi-5.18: switch to version tag=v5.18.8
* sunxi-5.18: add new megous patches
* switch to v5.18.5: exclude a previously applied patch
* fix: tools/mk_format_patch: numbered=false by default
* sunxi-5.18: rebasing and extraction using the mk_format_patch script
* Refactor patches
* Fix bug: the USB closed to the HDMI doesn't work
* Fix bug: cpufreq doesn't work
* Fix bug: thermal_zone doesn't work
* More frequency governors
* Add bootscript
* Fix bug: add missing dependency
needed for gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf
* sunxi-5.18: rebase megous patces to v5.18.3
* sunxi-5.18: Add upstream patches - tag: orange-pi-5.18-20220609-1318
* Check applicability to version 5.18.3
* sunxi-5.18: switch to version 5.18.3
* Update kernel configs
* Switch sunxi edge to 5.18.y
* Move sunxi to 5.18.y and re-enable AUFS
* Change version - temporally to make a build from here
* Update config
* 88xx was fixed in the mean time.
* Put version back
* Fix sunxi legacy, disable aufs on 5.10.y since its broken
* Upstream changed in the mean time
* Add a patch to enable 8821cu compilation at 5.18
https://github.com/armbian/build/pull/3814
* Re-enable CONFIG_RTL8822BU in edge
* Update CONFIG_RTL8XXXU
* Bump imx6
* Bump uefi kernels to 5.18.y
* Bump mvebu64 and switch odroid xu4 to 5.18
* sunxi-5.18 Initial state for armbian patches
* Adapting patches to the new kernel, sort, add new megous patches
* DEBUG
* Add the latest patches
* fix: compile error
drivers/spi/spi.c:3548:3: note: in expansion of macro ‘dev_info’
dev_info(&spi->dev, "spi_setup / gpio_is_valid(%d) ... doing gpio_request ...\n", spi->cs_gpio);
^~~~~~~~
drivers/spi/spi.c:3549:9: error:
implicit declaration of function ‘gpio_request’;
did you mean ‘gpio_to_desc’? [-Werror=implicit-function-declaration]
ret = gpio_request(spi->cs_gpio, dev_name(&spi->dev));
^~~~~~~~~~~~
gpio_to_desc
drivers/spi/spi.c:3549:27: error:
‘struct spi_device’ has no member named ‘cs_gpio’;
did you mean ‘cs_gpiod’?
ret = gpio_request(spi->cs_gpio, dev_name(&spi->dev));
^~~~~~~
cs_gpiod
drivers/spi/spi.c:3554:4: error:
implicit declaration of function ‘gpio_direction_output’;
did you mean ‘gpiod_direction_output’? [-Werror=implicit-function-declaration]
gpio_direction_output(spi->cs_gpio,
^~~~~~~~~~~~~~~~~~~~~
gpiod_direction_output
drivers/spi/spi.c:3554:31: error:
‘struct spi_device’ has no member named ‘cs_gpio’;
did you mean ‘cs_gpiod’?
gpio_direction_output(spi->cs_gpio,
^~~~~~~
cs_gpiod
In file included from ./include/linux/device.h:15,
from drivers/spi/spi.c:8:
drivers/spi/spi.c:3556:79: error:
‘struct spi_device’ has no member named ‘cs_gpio’;
did you mean ‘cs_gpiod’?
* Remove pre-applied patches
* sunxi-5.17: update and switch to version 5.17.11
* remove the patch that appeared in the upstream kernel
upstream commit c06a99a6605f524ff5ef096646e9501fc905366e
* sunxi-5.17: Fix include uapi spi spidev module
* add a compatible string alias "spi-dev" for spidev module
* overlay: Change the string compatible "spidev" to "spi-dev"
* remove unused patches
* drv: spi: spidev: fix header uapi
* Add alias "spi-dev" for module spidev
Add the armbian alias "spi-dev" to load and
initialize the spidev module from the device tree.
* Move patches for orangepi3-lts to series
* Remove unused patches
This resolves a bug that affects r8153b USB network interface causing the RX interface to hang on load.
On some xHCI controllers (e.g. Rockchip RK3399/RK3328/RK1808),
they need to enable the ENT flag in the TRB data structure
to force xHC to prefetch the next TRB of a TD.
The quirk patch is already applied to dwc3 xhci usb on rockchip64.
Enable the quirk on RK3328 through device tree node properties in rk3328.dtsi
* sunxi-5.17: Add series patches rtw88, rtw89 drivers
* Fix sunxi-5.17 for v5.17.4 version
* Print the error message and its contents
* rtl8822bs: used if kernel version less 5.16
Restrict the use of the wifi driver" "rtl8822bs" for
the kernel version less than 5.16
* Add reg_ahci_5v status okay for bananapro board
* Bananapro: add AXP209 regulators
* Fix series.conf, Disable the patch that is not being applied.
* Fix linux-sunxi64-edge.config for v5.17.3
* Fix linux-sunxi-edge.config to v5.17.3
* Switch EDGE to core 5.17 for sunxi
* Remove the old rtl8723cs driver which is incompatible with the new kernel and cannot be used.
* Use AUFS if the kernel version is less than 5.16
* Print the last 20 lines of the log if the kernel compilation failed.
* Set KERNEL_VERSION_LEVEL to 5.17
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Add 88 new patches to series. tag: orange-pi-5.17-20220409-0454
* Fix the applicability of patches.megous to the v5.17.3 kernel
* Fix series.conf. Disable the patch that is not being applied
* Add support for sun50i-h6-orangepi-3-lts
* Check the applicability in the series
* Move to a patches.armbian folder
* Bananapro: add AXP209 regulators
* fix-gpio-kconfig remove if EXPERT to allow normal build
* sunxi-5.17: Remove unused patches
* 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
* sunxi-5.15: Add reg_ahci_5v status okay for bananapro board
* Bananapro: add AXP209 regulators
* Fix series.conf, Disable the patch that is not being applied.
* sun7i-a20-bananapro: add reg_ahci_5v for sunxi-5.10
* sun7i-a20-bananapro: Add more regulators
* Rename patches for correct apply
* Disable the patch that is not being applied.
The patch is initially a crude hack. It solves one problem but creates
other problems. I don't know how to resolve the conflict correctly yet,
so I just disabled it.
add CONFIG_GPIO_SYSFS=y to linux-sunxi64-current.config and linux-sunxi64-edge.config
remove if EXPERT from /sys/class/gpio/... (sysfs interface) in /drivers/gpio/Kconfig
* The initial state of a series of patches for sunxi-5.17
tag orange-pi-5.17-20220323-1423
* DEBUG for sunxi-5.17
* Add Armbian patches to 5.17
* Fix duplicate nodes for sun50i-h5-orangepi-pc2
* Fix reg_ahci_5v to status okay for bananapro board
* Remove an unused patch for an unsupported sun50i-h6-tanix-tx6 board
* Fix duplicate nodes for sun50i-h5-orangepi-pc2
* Remove unused patch for pinctrl: sunxi: Fix deadlock.
This fix duplicates the upstream commit
896d1b8a36129c3f1378fbbafd7c394a877635b5 of the linux-5.15.y branch
pinctrl: sunxi: Use unique lockdep classes for IRQs
commit bac129dbc6560dfeb634c03f0c08b78024e71915 upstream.
This driver, like several others, uses a chained IRQ for each GPIO bank,
and forwards .irq_set_wake to the GPIO bank's upstream IRQ. As a result,
a call to irq_set_irq_wake() needs to lock both the upstream and
downstream irq_desc's. Lockdep considers this to be a possible deadlock
when the irq_desc's share lockdep classes, which they do by default:
============================================
WARNING: possible recursive locking detected
5.17.0-rc3-00394-gc849047c2473 #1 Not tainted
...
* Add to series.armbian Fix-duplicate-nodes-for-sun50i-h5-orangepi-pc2.patch
The problem with duplicate nodes in the device tree is that the first
one in the queue will be applied. The subsequent one will be ignored,
not replaced.
Fix spi-nor node initialization error for orangepi-pc2
[ 1.288263] spi-nor spi0.0: supply vdd not found, using dummy regulator
[ 1.306391] spi-nor spi0.0: mx25l1606e (2048 Kbytes)
[ 1.845203] Freeing initrd memory: 10824K
[ 1.855263] sun6i-spi 1c68000.spi: chipselect 0 already in use
[ 1.861159] spi_master spi0: spi_device register error /soc/spi@1c68000/spi-flash@0
[ 1.868842] spi_master spi0: Failed to create SPI device for /soc/spi@1c68000/spi-flash@0
Remove duplicate nodes from applied patches for the board
sun50i-h5-orangepi-pc2. After this fix:
[ 1.290252] sun50i-h5-pinctrl 1c20800.pinctrl: supply vcc-pc not found, using dummy regulator
[ 1.291250] spi-nor spi0.0: supply vdd not found, using dummy regulator
[ 1.310397] spi-nor spi0.0: mx25l1606e (2048 Kbytes)
[ 1.845686] Freeing initrd memory: 10824K
[ 1.854333] 2 fixed-partitions partitions found on MTD device spi0.0
[ 1.854369] Creating 2 MTD partitions on "spi0.0":
[ 1.854381] 0x000000000000-0x000000100000 : "uboot"
[ 1.855679] 0x000000100000-0x000000200000 : "env"
* Remove unused pinctrl-sunxi-Fix-misleading-lockdep-deadlock-warnin.patch
The problem was solved in the upstream kernel.
commit e221ef82d9f5e97bca61f7c25e2b58b04466de87 linux-5.16.y branch.
commit bac129dbc6560dfeb634c03f0c08b78024e71915 upstream.
This driver, like several others, uses a chained IRQ for each GPIO bank,
and forwards .irq_set_wake to the GPIO bank's upstream IRQ. As a result,
a call to irq_set_irq_wake() needs to lock both the upstream and
downstream irq_desc's. Lockdep considers this to be a possible deadlock
when the irq_desc's share lockdep classes, which they do by default:
============================================
WARNING: possible recursive locking detected
5.17.0-rc3-00394-gc849047c2473 #1 Not tainted
...
* Fix spi-nor node initialization error for orangepi-pc2
[ 1.288263] spi-nor spi0.0: supply vdd not found, using dummy regulator
[ 1.306391] spi-nor spi0.0: mx25l1606e (2048 Kbytes)
[ 1.845203] Freeing initrd memory: 10824K
[ 1.855263] sun6i-spi 1c68000.spi: chipselect 0 already in use
[ 1.861159] spi_master spi0: spi_device register error /soc/spi@1c68000/spi-flash@0
[ 1.868842] spi_master spi0: Failed to create SPI device for /soc/spi@1c68000/spi-flash@0
Remove duplicate nodes from applied patches for the board
sun50i-h5-orangepi-pc2. After this fix:
[ 1.290252] sun50i-h5-pinctrl 1c20800.pinctrl: supply vcc-pc not found, using dummy regulator
[ 1.291250] spi-nor spi0.0: supply vdd not found, using dummy regulator
[ 1.310397] spi-nor spi0.0: mx25l1606e (2048 Kbytes)
[ 1.845686] Freeing initrd memory: 10824K
[ 1.854333] 2 fixed-partitions partitions found on MTD device spi0.0
[ 1.854369] Creating 2 MTD partitions on "spi0.0":
[ 1.854381] 0x000000000000-0x000000100000 : "uboot"
[ 1.855679] 0x000000100000-0x000000200000 : "env"
* Add meson64 patch net: phy: meson-gxl: fix interrupt handling in forced mode
https://patchwork.kernel.org/project/linux-amlogic/patch/04cac530-ea1b-850e-6cfa-144a55c4d75d@gmail.com/
This PHY doesn't support a link-up interrupt source. If aneg is enabled
we use the "aneg complete" interrupt for this purpose, but if aneg is
disabled link-up isn't signaled currently.
According to a vendor driver there's an additional "energy detect"
interrupt source that can be used to signal link-up if aneg is disabled.
We can safely ignore this interrupt source if aneg is enabled.
This patch was tested on a TX3 Mini TV box with S905W (even though
boot message says it's a S905D).
This issue has been existing longer, but due to changes in phylib and
the driver the patch applies only from the commit marked as fixed.
Fixes: 84c8f773d2dc ("net: phy: meson-gxl: remove the use of .ack_callback()")
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
* Add meson64 kernel patch: net: phy: meson-gxl: improve link-up behavior
https://patchwork.kernel.org/project/linux-amlogic/patch/e3473452-a1f9-efcf-5fdd-02b6f44c3fcd@gmail.com/
Sometimes the link comes up but no data flows. This patch fixes
this behavior. It's not clear what's the root cause of the issue.
According to the tests one other link-up issue remains.
In very rare cases the link isn't even reported as up.
Fixes: 84c8f773d2dc ("net: phy: meson-gxl: remove the use of .ack_callback()")
Tested-by: Erico Nunes <nunes.erico@gmail.com>
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
drivers/net/phy/meson-gxl.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
* This is already contained in the 5.15.27 kernel
pinctrl: sunxi: Use unique lockdep classes for IRQs
commit 896d1b8a36129c3f1378fbbafd7c394a877635b5 linux-5.15.y
commit bac129dbc6560dfeb634c03f0c08b78024e71915 upstream.
This driver, like several others, uses a chained IRQ for each GPIO bank,
and forwards .irq_set_wake to the GPIO bank's upstream IRQ. As a result,
a call to irq_set_irq_wake() needs to lock both the upstream and
downstream irq_desc's. Lockdep considers this to be a possible deadlock
when the irq_desc's share lockdep classes, which they do by default:
============================================
WARNING: possible recursive locking detected
5.17.0-rc3-00394-gc849047c2473 #1 Not tainted
--------------------------------------------
init/307 is trying to acquire lock:
c2dfe27c (&irq_desc_lock_class){-.-.}-{2:2}, at: __irq_get_desc_lock+0x58/0xa0
but task is already holding lock:
c3c0ac7c (&irq_desc_lock_class){-.-.}-{2:2}, at: __irq_get_desc_lock+0x58/0xa0
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&irq_desc_lock_class);
lock(&irq_desc_lock_class);
*** DEADLOCK ***
May be due to missing lock nesting notation
4 locks held by init/307:
#0: c1f29f18 (system_transition_mutex){+.+.}-{3:3}, at: __do_sys_reboot+0x90/0x23c
#1: c20f7760 (&dev->mutex){....}-{3:3}, at: device_shutdown+0xf4/0x224
#2: c2e804d8 (&dev->mutex){....}-{3:3}, at: device_shutdown+0x104/0x224
#3: c3c0ac7c (&irq_desc_lock_class){-.-.}-{2:2}, at: __irq_get_desc_lock+0x58/0xa0
stack backtrace:
CPU: 0 PID: 307 Comm: init Not tainted 5.17.0-rc3-00394-gc849047c2473 #1
Hardware name: Allwinner sun8i Family
unwind_backtrace from show_stack+0x10/0x14
show_stack from dump_stack_lvl+0x68/0x90
dump_stack_lvl from __lock_acquire+0x1680/0x31a0
__lock_acquire from lock_acquire+0x148/0x3dc
lock_acquire from _raw_spin_lock_irqsave+0x50/0x6c
_raw_spin_lock_irqsave from __irq_get_desc_lock+0x58/0xa0
__irq_get_desc_lock from irq_set_irq_wake+0x2c/0x19c
irq_set_irq_wake from irq_set_irq_wake+0x13c/0x19c
[tail call from sunxi_pinctrl_irq_set_wake]
irq_set_irq_wake from gpio_keys_suspend+0x80/0x1a4
gpio_keys_suspend from gpio_keys_shutdown+0x10/0x2c
gpio_keys_shutdown from device_shutdown+0x180/0x224
device_shutdown from __do_sys_reboot+0x134/0x23c
__do_sys_reboot from ret_fast_syscall+0x0/0x1c
However, this can never deadlock because the upstream and downstream
IRQs are never the same (nor do they even involve the same irqchip).
Silence this erroneous lockdep splat by applying what appears to be the
usual fix of moving the GPIO IRQs to separate lockdep classes.
Fixes: a59c99d9eaf9 ("pinctrl: sunxi: Forward calls to irq_set_irq_wake")
Reported-by: Guenter Roeck <linux@roeck-us.net>
Signed-off-by: Samuel Holland <samuel@sholland.org>
Reviewed-by: Jernej Skrabec <jernej.skrabec@gmail.com>
Tested-by: Guenter Roeck <linux@roeck-us.net>
Link: https://lore.kernel.org/r/20220216040037.22730-1-samuel@sholland.org
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
* This is already contained in the 5.16.13 kernel
pinctrl: sunxi: Use unique lockdep classes for IRQs
commit e221ef82d9f5e97bca61f7c25e2b58b04466de87 linux-5.16.y.
commit bac129dbc6560dfeb634c03f0c08b78024e71915 upstream.
This driver, like several others, uses a chained IRQ for each GPIO bank,
and forwards .irq_set_wake to the GPIO bank's upstream IRQ. As a result,
a call to irq_set_irq_wake() needs to lock both the upstream and
downstream irq_desc's. Lockdep considers this to be a possible deadlock
when the irq_desc's share lockdep classes, which they do by default:
============================================
WARNING: possible recursive locking detected
5.17.0-rc3-00394-gc849047c2473 #1 Not tainted
--------------------------------------------
....
* rk322x: restore drm patches, rework a couple of hunks due to upstream changes
* rockchip: restore drm patches, rework hunks due to upstreamed patch
* Revert also on media kernel
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Add megous files for 5.16, tag orange-pi-5.16-20220216-2000
* Optimize the selection of a set of patches
* Remove unused patches
* Fix the state on the version tag=v5.16.11
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.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>
* Switched rockchip64-current to linux 5.15
* Backported and adjusted patches from rockchip64-current
* Switched rockchip64 edge to 5.16.y (#3499)
* Initial rockchip64-edge at 5.16.y
* Bunch of fixes for rockchip64-edge at 5.16.y
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.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>
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
* remove incorrectly duplicated GPIO pins from I2C7, name I2C7/I2C8 bus, from README.rockchip-overlays
Co-authored-by: Leif Sawyer <leif@akhepcat.com>
* Prepare xu4 edge for 5.16.y, move current of imx6 to 5.15.y and edge to 5.16.y
- fix bootsplash on 5.16.y
* rk322x: advance current to 5.15 and edge to 5.16
* rockchip: advance current kernel to 5.15, edge to 5.16
* - adjust configs
- fix bootsplash patches
- adjust aufs
* Switch sunxi / sunxi64 current to 5.15.y, edge to 5.16.y
- cleanup bootsplash patches
- adjust configs
* Update mvebu64
Co-authored-by: Paolo Sabatino <paolo.sabatino@gmail.com>
* Add new patches from the tag orange-pi-5.16-20220205-1958
* Remove mutually exclusive patches
* Add, sort next patches for series armbian 5.16
* Add next armbian patches to series.conf
* Swich BRANCH for sunxi: legacy=5.10 current=5.15 edge=5.16
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Add upstream megous 5.16 patch to 5.15
* Add wifi rtl8723cs patches to series armbian
* Add a new one, remove old patches that are already in the kernel
* Add redesigned patches for 5.15 to the armbian series
* Remove unused patches
* Finish line
* The old rtl8723cs driver is disabled by default.
* Enable the old rtl8723cs driver by default.
* Comment enable\disable the old driver rtl8723cs-old
* Revert "Swich BRANCH for sunxi: legacy=5.10 current=5.15 edge=5.16"
This reverts commit aad1e92b5e.
* Remove an aged patch from use #3443
Allwinner-Add-frame-inversion-to-correct-audio-chann.patch
* Rename and prepare for the series 5.15
* Split and rename files for sun50i-h616-dtsi
* Split and rename files for sunxi overlays
* Remove mutually exclusive patches
* Add fifty redesigned patches to the series
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Remove fifty-four old patches
* Fix compile error
* Delete unused ones and sort if possible for megous series
* sunxi-5.15: Sort, fix compile warning, remove unused
* Rework print log for patching
* Recycling of megous v5.16.4 patches
The patches were sorted as far as possible. Some patches are renamed
according to their place of application. The length of the patch name
has been changed to improve readability using
the `git format-patch --filename-max-length=75` method.
The folder containing the patches will have the name `patches.name`
and the corresponding file `series.name` for the convenience
of processing and moving them upstream. But the control file remains
`series.conf`.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Add a series of armbian patches for 5.16
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Remove patches whose fixes are already in the kernel
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Support edge kernel for Rock 3A and rk35xx
* Removing patch email headers
There is also some script floating around to do this automatically when pooling from patchwork
* Update rk356x-usb2-support.patch
* Remove email headers
* Remove email headers
* Remove email headers
* Update config and change edge branch
* Enable edge beta build
* Refresh the rk35xx patches and update the dts
Remove also previous wireless patches related to IPX removal
* Removing hirsute target
deprecated
Co-authored-by: Catalin Toda <catalinii@yahoo.com>
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* waiter_local_repo: Fixed incomplete logic
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* A series of patches for sunxi v5.15.16
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* DEBUG
* check 70
* check 101
* Add 101 Armbian patches as series
Patches are renamed using the logic of the file structure
and the essence of the changes, sorted in the order
of their receipt. Fixed a lot of incorrect overlay
of some pieces in patches. Several small patches are
combined, because they changed one file.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Remove old patches that have been reworked into a series
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Fix for apply to v5.15.17
* Two Bluetooth-BTRTL patches for sunxi will be applied in the series.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* check 113
* Fix print output
* Revert "DEBUG"
This reverts commit 49e2c7fdc0.
Fix the dts to match board's reference design:
- update vddio_boot regulator to 3.3v (Wi-Fi SDIO module)
- add vccq_1v8 regulator with 1.8v for eMMC SDIO
In the first revision of JetHub D1 the vccq_1v8 regulator was 3.3v.
All installed eMMC modules were tested to work in HS200 mode at 3.3v
supply voltage. In the next revisions of the device eMMC will be
powered with 1.8v according to the standard.
* Add initial series patches for sunxi-5.16
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Now all patches are applied to the v5.16 kernel without errors
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Handle an exception if the initial tag is the top of the branch.
Remove the handling of the old exception.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* sunxi64_common.inc: Fix for 5.16
* sunxi-common.inc: Fix for 5.16
* Revert debug for EDGE: KERNEL_VERSION_LEVEL to "5.15"
* Add new patches from megous and switch to v5.16.1
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* waiter_local_repo: Fixed comment
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Several improvements for RPi builds
- attach to RPi kernels
- current (ubuntu) -> legacy
- current -> 5.10.y, edge, 5.15.y
* Move current Rpi to 5.15.y and edge to 5.16.y
* 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.
* Remove the garbage from the `install.log` file
You cannot use `--info=progress2` for the `rsync`
command when all output is sent to a file.
This creates a large garbage file.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Changes megous reverse commit. Just disable the patch
commit bd592ec43b76b298be29126e667850113b84376d (tag: orange-pi-5.15-20211125-1352)
Author: Ondrej Jirman <megous@megous.com>
Date: Thu Nov 25 13:51:59 2021 +0100
Revert "rtw88: Add more channels"
This reverts commit cb1e3839822d4f782a9af6c27568540414093ba6.
* Revert "Calculate patches changes only on first level since this fails when including subfolder. Bug in sort. Needs to be reworked once"
Return `megous` patches
This reverts commit 2eae831889.
* Sunxi 5.10: Fix ISO C90 forbids mixed declarations and code
* extensions framework (née "fragments")
- this should actually change nothing at this point, just add capabilities
- the framework is implemented in lib/extensions.sh
- the "if function x exists then call x" replaced with call_extension_method()
- +inline documentation
- +compatibility names
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* extensions framework; meta-extensions: auto-docs and sample extension gen
- 2 extensions dealing with extensibility itself
- detect-unused-extensions: shows which extensions are enabled, but never called.
- gen-sample-extension-docs: generates a sample empty extension & Markdown documentation for extensions
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* new extension methods and features via config variables in core Armbian
- `SKIP_EXTERNAL_TOOLCHAINS=yes` - does not download or use any linaro toolchains, only build host-installed ones
- `SKIP_BOOTSPLASH=yes` - does not patch kernel for splash file
- `EXTRA_BSP_NAME=xyz` - allows for BSP variants, useful for when extensions modify the BSP
- `EXTRA_ROOTFS_MIB_SIZE=x` - add x mib's to rootfs size, for use with very small images
- `KERNEL_EXTRA_TARGETS` - what extra targets to make kernel for, default to "modules dtbs"
- `BOOTCONFIG=none` - does not build nor install u-boot; also doesn't handle bootscripts et al
- `unset KERNELSOURCE` - does not build nor install kernel, nor build initrd, nor build nor install firmware
- `ARMHF_ARCH=skip` - does not add armhf to apt/dpkg, thus pure arm64
- `SKIP_ARMBIAN_REPO=yes` - results in armbian.list.disabled in the final image
- define `APT_EXTRA_DIST_PARAMS` with apt-cacher-ng options and use it for `PACKAGE_LIST_INSTALL/REMOVE` et al
- initial support for targeting x86/amd64 UEFI and BIOS
- some do's/don'ts for x86/amd64, like a different `UBUNTU_MIRROR` default
- GPT/EFI(ESP) partitions (fat, `UEFISIZE=256` to enable, mount `UEFI_MOUNT_POINT=/boot/efi`, first on disk but ends
up at `$uefipart`=15)
- GPT/BIOS partitions (fat, `BIOSSIZE=1` to enable, second on disk but ends up at partition 14)
- `UEFI_FS_LABEL="armbiefi"` - to set the FAT label for the EFI partition, visible in Win/Mac
- hard-requires gdisk package host-side
- add add_host_dependencies() extension method; fill `EXTRA_BUILD_DEPS="pkg pkg2"` to install to host before toolchains
download
- add pre_prepare_partitions() extension method, for custom partition size calculations
- add create_partition_table() extension method, used to do full-custom partitioning if `USE_HOOK_FOR_PARTITION=yes`
- add post_create_partitions() extension method, mostly for easy debugging
- add post_write_sdcard() extension method, where you can also set `SKIP_VERIFY=yes` to skip sdcard verification
- add post_install_kernel_debs() extension method.
- multiple fixes to bsp to avoid spurious errors when files are not where it expects
- v4: detect `update-initramfs` failure and abort build with useful message if it does
- v4: show useful stacktrace in `exit_with_error`
- if `ERROR_DEBUG_SHELL=yes`, drop into a shell before unmounting/deleting everything, so we can inspect what went wrong
- v4: display a message before `apt-get remove PACKAGE_LIST_BOARD_REMOVE` packages, so any errors while removing are easy to understand
- v4: preserve kernel .config's dates when copying
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* extensions framework; refactor tool fetching/building into extensions
- a few examples of core refactoring using extensions
- sunxi-tools extension, enabled by 2 different sunxi family includes ("reuse" example)
- marvel-tools extension, enabled by 2 different mvebu family includes
- rkbin-tools extension, enabled by rockship64_common family include
- amlogic-fip/c2-blobs stuff refactored directly into meson64_common.inc ("single-use" example)
- removed the 'testings' fetch_from_repo completely since not used anywhere.
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* .wip's for UEFI arm64 and UEFI/BIOS x86 via new GRUB extension
- v3: added `growroot`-awareness to `armbian-resize-filesystem`
- the partition-growing part of `armbian-resize-filesystem` does not deal correctly with the UEFI layout
- `growroot` is installed on UEFI images by default, that handles growing partition during initramfs
- now `armbian-resize-filesystem` handles `resize2fs` only, and works.
- v4: reworked UEFI board/family/include structure:
- use Distro's `linux-generic` kernel only for `current`
- `edge` now builds it's own pure-mainline `5.15.y` kernel, for both x86 and arm64
- `.config` taken from Ubuntu, probably needs tuning for EXTRAWIFI=yes et al
- v4: introduce `SKIP_KERNEL_SYMLINK=yes`, tested in `builddeb`
- to avoid symlinking kernel; u-boot likes it, but grub and flash-kernel hates it
- v5: many fixes
- v7: more small fixes.
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* .wip for the RaspberryPi 4B via new flash-kernel extension
- this does not build it's own kernel "yet", but uses default linux-raspi kernel from Ubuntu
- flash-kernel is not really a bootloader
- it just prepares kernel et al a FAT partition for booting by the RPi4b bootloader
- flash-kernel is standard Debian package, but has only been tested on Ubuntu releases
- it is really only known-working since Hirsute release.
- Debian's rpi kernel is armhf only, so out of scope here, at least until we add source-built kernels.
- v3: fixed focal rootfs build. untested.
- v3: better variable names, preparing for source-built kernel.
- v5: new edge build with pure mainline kernel.
- v6: many fixes and some hacks for packaging and layout, also firmware (using Ubuntu's)
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* Added first patch to edge x86 related to wifi drivers
* extensions: leave hostapd alone; remove hackish ext; block reentrancy
- package-list-utils does not belong in this PR
- grub or bcm2711 is not the place to remove hostapd
- block recursive enable_extension() calls, for now.
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* gen-sample-extension-docs: fix: avoid counter in generated sample
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* extensions: dependencies: enable_extension() in extensions with a stack
- and better stacktraces, I hope
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* Remove code from package list since we don't have it in repository
Adjust kernel config to disable driver that needs further polishing.
* Allow amd64 to build the same desktops as aarch64. We only have this limit for armhf, where some desktops don't work
* amd64: allow building amd64 on aarch64 with system toolchain
- conditionally add gcc-x86-64-linux-gnu to hostdeps
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* add libelf-dev directly to hostdeps (and Dockerfile), remove extension
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* packaging: remove SKIP_KERNEL_SYMLINK hack, fix the root cause
- which was the missing $image_name for non-arm64 & non-arm, so: x86 for example
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* grub: really obliterate u-boot stuff from BSP
- for now. soon we'll refactor u-boot so not have to do this
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* flash-kernel: really obliterate u-boot stuff from BSP
- for now. soon we'll refactor u-boot so not have to do this
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* extensions: add host_dependencies_ready() hook
- this passes FINAL_HOST_DEPS containing all hostdeps for the run after they're installed
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* Add verification functions for correct selection.
* If UEFI Skip symlink creation
* Do not create dtb package for amd64
* Skip scripts folder cleaning if build process native.
Skip creating postinst prerm scripts for headers.
* Skip applying headers-debian-byteshift.patch if build native
* Fix architecture syntax as x86_64
* Revert "amd64: allow building amd64 on aarch64 with system toolchain"
This reverts commit 0c5ee20bb1.
* Compare architectures before starting compilation.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* extensions: cleanups after fixes by the-Going
- packaging:
- there is _no need_ anymore for the symlink hack, CONFIG_EFI or no. But check is great, see below
- it's not `amd64` that has no DTB's, it's all UEFI, thus: `is_enabled CONFIG_EFI`, thanks!
- Explicitly disallow "reverse cross compile" in amd64.conf.
- whitespace-only-deletions: revert. we shall shellfmt the whole thing one day, but not today.
- fix a few syntax warnings in newly introduced code (floating `$ARCH` vs `"${ARCH}`) - blame shellcheck
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* packaging: fix: turns out a lot of boards have CONFIG_EFI=y, can't use that for dtb/no-dtb decision.
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* grub: remove debug
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* firmware: allow installing `armbian-firmware-full`; make it really full
- can now use `BOARD_FIRMWARE_INSTALL="-full"` to install full firmware for the board. enable for UEFI.
- don't rely on KERNELSOURCE for firmware-related decisions. introduce `INSTALL_ARMBIAN_FIRMWARE` which defaults to `yes`
- rpi4b/flash-kernel: disable Armbian firmware; we need linux-firmware-raspi2, which conflicts.
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* extensions: log to /${LOG_SUBPATH}/ instead of fixed /debug/
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* extensions: introduce cleanup_extension_manager() called by build-all-ng's unset_all()
- to reset/unset everything done by the the initializer, so build can run again
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* extensions: remove 'global' logging, for use with build_all_ng
- enable_extensions() will have to live on without logging to file. it's just too early.
- now init EXTENSION_MANAGER_TMP_DIR in initialize_extension_manager()
- now init EXTENSION_MANAGER_LOG_FILE in initialize_extension_manager()
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* extensions: build-all-ng.sh bugfix due to extension's debug to stdout
- extensions (among other things) can produce output to stdout when activated
- fix: check_hash() produced "idential" (sic, now changed to IDENTICAL) to stdout as a trigger
- debugging output got mixed with "idential", rendering hash cache void for families that used extensions
- eg: sunxi, others
- fix is to send stdout to the bitbucket when sourcing the board & arch config files
- proper fix would be stop using stdout in this case and use return code for check_hash()
- one day soon
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* Add CI build targets
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
Co-authored-by: The-going <48602507+The-going@users.noreply.github.com>
All warning:
debug> grep warning: compilation.log | wc -l
152
A large number of garbage warnings:
debug> grep warning: compilation.log | grep IEEE80211_MAX_AMPDU_BUF | wc -l
103
After v4.19 linux kernel, this definition is not required.
Check:
list="$(find drivers/net/wireless/realtek/ -type f)"
for f in $list;do awk -v f=$f '/IEEE80211_MAX_AMPDU_BUF/{print f}' $f;done
drivers/net/wireless/realtek/rtlwifi/base.c
drivers/net/wireless/realtek/rtl8723cs/include/wifi.h
Only one drivers/net/wireless/realtek/rtlwifi/base.c file uses
the definition IEEE80211_MAX_AMPDU_BUF_HT.
or
See `git log -p b8042b3da925f390c1482b -3` command in
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
* Rework patches for sunxi 5.15.4
* Rework patches sunxi for 5.15.5
* Kernel switch tag=v5.15.5 for sunxi EDGE
* Temporarily disabled, requires rework.
drivers/clk/sunxi-ng/sun8i-de33.c: In function ‘sunxi_de33_clk_probe’:
drivers/clk/sunxi-ng/sun8i-de33.c:155:8:
error: implicit declaration of function ‘sunxi_ccu_probe’;
did you mean ‘of_sunxi_ccu_probe’? [-Werror=implicit-function-declarati>
ret = sunxi_ccu_probe(pdev->dev.of_node, reg, ccu_desc);
^~~~~~~~~~~~~~~
of_sunxi_ccu_probe
cc1: some warnings being treated as errors
make[3]: *** [scripts/Makefile.build:277:
drivers/clk/sunxi-ng/sun8i-de33.o] Error 1
make[2]: *** [scripts/Makefile.build:540: drivers/clk/sunxi-ng] Error 2
* Correct the comment.
* Add a series of patches for sunxi 5.10
Patches from the repository
https://github.com/megous/linux branches of orange-pi-5.10
* Patches adapted to the kernel version v5.10.81
* Remove unnecessary patches 5.10.19-5.10.75
* Kernel switch tag=v5.10.81 for the current sunxi
* Adjust broken patches, build tested on sunxi and sunxi64
* Remove patch added by mistake
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Add new function apply_patch_series
* Apply a series of patches if a series.conf file exists
* Add all megous orange-pi-5.15 branch patches as series
* Add an Exception for version 5.15 for sanxi
* Adjust the switch for sunxi
* Fix megous patches series for v5.15.3
* Switch version to 5.15.3 for sunxi
* Check the exception for 5.15 sunxi
* rework to fix regulator and frequency issues
* rework nanopi-r2s, roc-cc and roc-pc patches to accomodate dmc dtsi changes
* map gpu as cooling device
* fix dmc 600 Mhz opp node min voltage
* imported Rockchip project patches from libreelec
* disable duplicate/unapplicable patches and rework others
* add patches for tinkerboard, miqi and xt-q8l-v10 to enable hevc, hevc_mmu and rga nodes
- starting from Home Assistant OS (HASSOS) setup/patchset, which is stable with pure-mainline
- *huge thanks* to Stefan Agner (@agners) from Home Assistant for his work and help with this
- CONFIG_DRM_MESON=y fixes the order of shutdown callbacks, allowing it to reboot without patches
- this increases the kernel size a bit, due to some dependencies like DRM=y
- remove the shutdown revert patch, allowing other meson64 boards to mainline-reboot
- add fdt/no-map patch fixing the dreaded "SError Interrupt on CPU4" panics that plagued the N2
- move the N2 to mainline u-boot on current (rebased, already done)
- add SPI-enabling DTB variants, which allow writing to SPI NOR flash (and usage instructions in comments)
- add UBOOT_TARGET_MAP and write_uboot_platform_mtd to current, for nand-sata-install to SPI/USB goodness
- remove the UHS-enabling patch, to avoid 1.8v vs 3.3v mess. Make sure to use only A1-rated SD cards as recommended.
- change default cpufreq governor for 24h+ stability
- other patch cleanups:
- move deprecated/non-applying patch to need-check
- remove the HardKernel ODROID-specific reboot driver and DTS patches (odroid-reboot.c) which are now useless.
- remove documentation-only patches (we have enough patches in meson64 without those)
- remove duplicated SAR ADC patches
- remove multiple different and conflicting patches for DTS and emulated-PWM GPIO fan
- now using simple on/off GPIO fan at 30 celsius, unrelated to passive cooling
* remove 0-rever-rk3328.dtsi-.patch
* split rk3328-dtsi-mmc-vdec-usb3-tweaks.patch into different specific patches (sdmmc-ext, mmc-reset, power domains, usb3 resets)
* split rk3328-audio-and-renegade-supplies.patch into specific roc-cc audio and supplies patch and general rk3328 spdif patch
* add "dtsi" infix to rk3328 patches that deal with dtsi files
* add back mali gpu operating points patch
* add workaround against default MAC Address (userland utility bdaddr does not work to set MAC Address as expected)
* enable bits for xt-q8l-v10 board (ap6330/bcm4330 part), switching AP6330 bluetooth to btbcm driver using serdev
facilities to avoid userspace machinery with deprecated hciattach tool, added bits to enable driver support in kernel.
Removed ap6330 bluetooth service from bsp packages, added initramfs-tools hook to include bcm4330b1.hcd firmware in initramfs
* Backporting patch to 5.10 kernel makes sense. Lets do it.
Co-authored-by: iamdrq <iamdrq@qq.com>
Co-authored-by: Igor Pecovnik <igor.pecovnik@gmail.com>
* Bumping EDGE kernel to 5.14.y
Meson64:
- removing Odroid reboot shutdown patch since its probably not needed anymore
Rockchip64:
- removing Rockpi S. No interest to maintain this any further
- removing PBP suspend. Doesn’t align. Need inspection if some other way was mainstreamed
- temporally removing Orangepi R1
* Re-adding rockpis, pbp suspend, HFLPS170 wifi and cleanup
* Removing deprecated patch, fixing ap6256 wifi
* Re-enable Opi R1 plus, untest
* Add and fix Radxa Zero
* 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>
- fix/dup bootscript, since new u-boot fixed n2_plus to n2-plus variant
- g12b: if n2 and edge, enable new u-boot; include non-SD version as SPI binary; write_uboot_platform_mtd
- Kernel DTS patch to add SPI-flash-enabled DTBs (slower eMMC), produces -spi .dtbs for n2 and n2-plus
- This could also be an overlay, but I dunno overlays.
- SPI+USB3 boot works with "pendrive" storage, untested with cabled/high power USB->SATA or USB->NVMe
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* [ meson64 ] nanopi K2 ethernet fix
Fix NanoPi K2 Ethernet issues
Do some cleanup of the Meson64 folder while at it
* [ Meson64 ] revert accidental delete of C2 audio patch
* [ RK3328 ] boost GPU voltages to avoid starving Memory controller
The RK3328 has the dynamic memory controller and GPU on the same power rail.
Both are able to be dynamically clocked, both have opp tables.
- DMC min voltage: 1.075V
- GPU min voltage: 0.950V
On boards with only the GPU enabled, they memory controller can be under-voltaged.
On boards attempting to use both, the disagreeing opps result in the GPU failing to init
This patch applies a mV range opp to the GPU and fixed opps to the DMC on rk3328-roc-cc
to allow everything to get alongin all possible devfreq situations.
* [ rockchip64 ] clean up disabled patches
* [ rock64 ] add mali supply and remove unused 5V supply
- New Mali opps will keep from starving ram controller
- extra supply was causing dmesg errors.
As it shares enable with another supply and both were marked "always on"
I removed the second. Neither are referenced by any ports/devices.
- add mtd-utils to PACKAGE_LIST_BOARD.
- this should be enough to wipe Petitboot;
- more investigative work and u-boot building is needed for SPI+SATA boot
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* Upgrading sunxi and sunxi64 EDGE to 5.13
Both variants tested for building
* Bump imx6 to 5.13.y
Tested
* Bump Jetson nano kernel to 5.13.y
* Move mvebu and mvebu64 edge to 5.13.y
