* Correcting the Perf unit's interrupt source number to 66 as stated in the Allwinner A10User manual to resolve conflict with Uart 2 which actually uses interrupt source number 3
* rename to all lower case and add in sun4i-emac dma support. Note that support only exist in the driver for the rx channel
* Ensure that sun4i patches actually implemented
Signed-off-by: Ryan L <ryestar101@gmail.com>
* Apply performance monitoring unit IRQ number patch to uboot
* Add patch for resolving the perf unit irq number to the edge kernel
Signed-off-by: Ryan L <ryestar101@gmail.com>
* Add sun4i emac ethernet DMA support to the edge kernel
Signed-off-by: Ryan L <ryestar101@gmail.com>
* Append missing .patch so that our patch is found and works properly
Signed-off-by: Ryan L <ryestar101@gmail.com>
* Apply EMAC DMA support and PMU fix to edge kernel
---------
Signed-off-by: Ryan L <ryestar101@gmail.com>
* rockchip64: add `BOOT_SCENARIO=binman` for mainline u-boot
- drop special handling for 3308's `legacy` branch
- rpardini: note how SPI/mtd is not yet supported for this scenario
Co-authored-by: Ricardo Pardini <ricardo@pardini.net> (squash/splits, shellfmt)
* `rock-s0`/`rockpi-s`: use `BOOT_SCENARIO=binman`; move blobs to armbian/rkbin
- Move rk3308 boot blobs to armbian/rkbin
- delete obsolete ones
- Alter rock-s0 and rockpi-s to use the new "binman" BOOT_SCENARIO
Co-authored-by: Ricardo Pardini <ricardo@pardini.net> (shellfmt; small fixes; squashes)
- Bump U-Boot from v2024.10-rc3 to v2024.10
- Move U-Boot patch dir to default one (`$BOOTBRANCH/board_$BOARD`) which gets applied automatically by the patcher for the specific $BOARD
- Little fixes: Use `declare -g` and a code style similar to NanoPi R6 series
Removed gpio-keys node (NOTE: add to the M4 Berry DTS)
Add vcc1v8 and vcc3v3 regulators
Fixup MMC nodes
Add bluetooth node (NOTE: BT is still iffy in Armbian)
Signed-off-by: Patrick Yavitz <pyavitz@gmail.com>
Re-extract the kernel patches as a series.
Re-extract the u-boot patches as "git format-patch" command.
Unified patch extraction makes it easier to work with patches.
- in main `rockchip64` family, for current/edge (6.6 / 6.11)
- using mainline u-boot's generic rk3568 for current/edge
- vendor kernel is added via a copypasta hook to piggyback on `rk35xx`
- requires armbian/linux-rockchip PR https://github.com/armbian/linux-rockchip/pull/245
- vendor u-boot:
- is required to bringup npu for vendor kernel (otherwise panics)
- .dts done based on vendor kernel DT + looking at armsom-sige3
- defconfig ripped off from armsom-sige3
There are three revs: AM-GZ80x, AM-GZ80x-US and SC-GZ80x
Add a DSTI in case one should drop out of the sky and we
need a DTS for it. This also removes its dependency on
meson-axg-jethome-jethub-j1xx.dtsi.
Can now power down via power button on the back of the
unit and power back on via reset button on the side.
Signed-off-by: Patrick Yavitz <pyavitz@gmail.com>
Add the A83T processor to the sunxi_mmc_can_calibrate
logic function for proper configuration.
Return the default settings of DRAM_CLK.
This code has been tested for bootloader v2024.01 and later.
* Gateway AM-GZ80x: Re-brand as Amper & update u-boot to v2024.04
During a search I noticed other companies are using the same
unit. Lets re-brand to Amper as technically that is the product
brand name.
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
* Delete old patch set: `patch: u-boot: v2023.10: board_gateway-gz80x`
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
* Update test target
---------
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
Co-authored-by: Patrick Yavitz <pyavitz@armbian.com>
Co-authored-by: Igor <igor@armbian.com>
Reference patch set: https://patchwork.ozlabs.org/project/uboot/list/?series=411513&state=*
Hopefully, other boards using same uboot-version can benefit from the added support.
**Note for Maintainers - to enable KASLR seed, you need:**
- `CONFIG_RANDOMIZE_BASE=y` configured in your kernel .config
- `CONFIG_CMD_KASLRSEED=y` and` CONFIG_DM_RNG=y` configure in your u-boot .config
- exposed crypto and rng nodes in you board's device-tree
- `kasrlseed` command before kernel boot in your boot.cmd
- `CONFIG_SECURITY_DMESG_RESTRICT=y` in kernel .config is also advisable
* KASRL-supported u-boot 2024.07 for everyone:
- move /chosen/kaslr-seed support patchset to general 2024.07 BOOTPATCHDIR
- attach nanopi-r5c and oprangepi5-plus BOOTPACHDIR to patches/uboot/v2024.07 general dir
* u-boot: patch nanopi-r5c-rk3568_defconfig and orangepi-5-plus-rk3588_defconfig to enable KASLR
* rewrite-uboot-patches nanopi-r5c/orangepi5-plus
* patches: uboot: Improve kaslrseed support for v2024.07
---------
Co-authored-by: ColorfulRhino <131405023+ColorfulRhino@users.noreply.github.com>
- since 792d9d9d Variables add to environment in post_config_uboot_target function are ignored.
- So setting the variable ATF_LOAD_ADDR doesn't work anymore
- ATF_LOAD_ADDR changed in the uboot patch instead
Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.com>
A boot.cmd file still needs to be created, but this is
functional.
Overlay support is now baked into the syslinux patch.
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
* To modify the PWM-fan temperature control policy of fine3399 to adjust the fan speed to a lower level
* Integrating support for xiaobaonas boards into the rockchip64-6.9 kernel
- rebased 2 patches
- moved null patches for dts & defconfigs to `dt` / `defconfig` dirs
- rename defconfigs since we're at it; use board-specific only
- defconfigs re-saved
- rebased 3 patches
- moved null patches for dts & defconfigs to `dt` / `defconfig` dirs
- don't rename defconfigs: those are shared with Joshua Riek (ubuntu-rockchip)
- defconfigs re-saved
* bump rk322x-box and rk3318-box to u-boot v2024.07-rc5
* leverage uboot relocation for rk3328
* rework hdmi/vop patches
* fix some usb issues on rk3318-box
* cleanup rk322x-box and rk3318-box old uboot patches
All remaining `media` boards have been integrated into the `rockchip64` family.
- Remove the family config
- Remove all kernel patch folders
- Remove all U-Boot patch folders
- Remove all kernel configs
- add `pre_config_uboot_target` hook for switching BOOTCONFIG across the two targets
- adapt `UBOOT_TARGET_MAP` to not call the defconfig Makefile targets directly, instead, just do a variable assignment (ignored by Make)
- otherwise, when using the defconfig directly in the `UBOOT_TARGET_MAP`, the `post_config_uboot_target` .config changes are overwritten when Make is called
- only patch left is boot usb-nvme-scsi/sata first (still done in meson64.h)
- remove FIP handling from family file `meson-sm1.conf` into board file hook where it belongs
- u-boot: enable more compression methods, EFI debugging, i2c, leds, tcp networking
- use flashcp for mtd writing
- Unchanged:
- confirmed as of v2024.04: using the C4 (not HC4) defconfig is still needed to be able to write to mtd when booted from SD
- also confirmed: one still needs to erase Petitboot using Petitboot, then boot from SD, to be able to flash mainline u-boot to mtd
- makes it compatible with vendor out-of-box blobs (which include TEE) in the from-factory eMMC
- Armbian itself doesn't ship TEE blobs
- when combining from-factory eMMC blobs with an Armbian SD card, TEE blobs are in practice found by u-boot
- but then proceeds to fail with `optee api revision is too low`
- disable OPTEE in defconfig fixes it, TEE isn't used in any way by Armbian
- makes it compatible with vendor out-of-box blobs (which include TEE) in the from-factory eMMC
- Armbian itself doesn't ship TEE blobs
- when combining from-factory eMMC blobs with an Armbian SD card, TEE blobs are in practice found by u-boot
- but then proceeds to fail with `optee api revision is too low`
- disable OPTEE in defconfig fixes it, TEE isn't used in any way by Armbian
uboot default behaviour is the assert resets when
it has to pass control to the kernel.
This may cause compatibility issues if the kernel
driver is not instructed to properly deassert the resets,
so we change the uboot behaviour for dwc and ehci usb
drivers to deassert reset on exit.
multitool utility uses the legacy/vendor 4.4 kernel
and it was failing to turn on HDMI properly.
Assert and deassert all vop and hmdi resets to clean
up the state on uboot exit seems to solve the issue
- we've had kernel patches/DT (from chewitt) for this in meson64 for a long time, but I never sent the board
- uses blobs for the `tartiflette-s912` which is also an DDR3 S912 (VIM2's blobs are DDR4 and won't boot)
- this adds `u-boot 2024.04` support, using chewitt's DT & `000.patching_config.yaml` & a specific BOOTPATCHDIR
- this is a full board as-if it was an SBC, and expects to boot from mainline u-boot;
- for that to work you've to wipe the eMMC and get rid of the vendor-supplied u-boot
- if this is not what you want/need, you can use the aml tvbox "board" instead, together with Android u-boot
- remove deprecated patches
It affects all boards that uses Radxa u-boot branch
@amazingfate
Perhaps also adjust armsom7 to this change to have less code maint?
This includes a patch that sets the maximum frequency to 24 MHz in U-Boot
which improves reliability as previously U-Boot would randomly fail
reading from the eMMC.
Signed-off-by: Martin Pietryka <martin@pietryka.at>
- `mmc-sdhci-allow-disabling-sdma-in-spl.patch` has landed in 3cd664dc92
- remove `CONFIG_SPL_MMC_SDHCI_SDMA=n`, as fix has landed in 3b804b370d (thanks Kwiboo for the pointer)
- use binman-produced binaries
- use `flashcp -p` to write fast to spi
- bump ATF (TF-A) to lts-v2.8.16
- configure /etc/fw_env.config userspace to SPI env coordinates
- configure /etc/fw_env.config userspace to SPI env coordinates
- include libubootenv-tool userspace for fw_printenv and fw_setenv
- use `bs=32k seek=1` instead of `seek=64` suggested by Kwiboo (thanks!) for speedy writing
- add a check for the u-boot.bin size (992KiB) suggested by Kwiboo (thanks!)
- really a close call: we're at 994.920 bytes right now
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
Co-authored-by: Jonas Karlman <jonas@kwiboo.se>
