Framework stores our base-files in rootfs cache with version that comes from trunk and when we make stable images for current or previous release, build fails with error E: Packages were downgraded and -y was used without --allow-downgrades.
* 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>
* youyeetoo r1 v3: add initial support for this board
* arch: arm64 board: youyeetoo r1 v3 replace edge with vendor kernel
* arch: arm64 board: youyeetoo r1 v3 reviews changes:
- Removed patch, see the pr for more details #7108
- Removed old kernel legacy
- WIP: Added DTS code on https://github.com/armbian/linux-rockchip/pull/223
I compiled the OS with latest changes, untested build logs in https://paste.armbian.com/ofidozaqup
* Update: Rename board from V3 to v3 (ARM64, Youyeetoo R1)
- Note: Untested on v1 as I don't have a v1 board available.
* Discord annoucement: push only when label "Needs review" is set
* Change to label triggering
* actions: Add run-name to `pr-announce` workflow
---------
Co-authored-by: ColorfulRhino <131405023+ColorfulRhino@users.noreply.github.com>
The workflow ran regardless whether `ARMBIAN_SELF_DISPATCH_TOKEN` was set or not, generating errors if the secret could not be found.
In addition, simplify and beautify the workflow.
- one is actually general fix - recommened installation of library before installing rockchip-multimedia
- second is holding package before running upgrade as it wants to pull older library from kde repositories
- remove KDE Neon base files upgrade pin
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>
* rockchip64: edge: rewrite kernel config
* rockchip64: edge: set CONFIG_SECURITY_DMESG_RESTRICT=y
Advised for KASLR-enabled kernels - no side effect for non-KASLR
* rockchip64: current: rewrite kernel config
* rockchip64: current: set CONFIG_SECURITY_DMESG_RESTRICT=y
Advised for KASLR-enabled kernels - no side effect for non-KASLR
The earlier attempt seem to limit announces to repository members for some reason.
This attempt limits to the repo only, therefore forks should not be affected.
Not sure if it works, but there is only one way to find out.
- linux-tqma-current.config: enable HDMI, LVDS, Bluetooth
- imx8_common.inc: use tag instead of branch (v6.6.43)
- fix asound.state.tqma
Signed-off-by: Martin Schmiedel <Martin.Schmiedel@tq-group.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>
On different boards, eMMC and SDcard memory devices can have
numbers 0, 1, 2 in any sequence.
SDcard -> 0; eMMC -> 2
SDcard -> 2; eMMC -> 0
SDcard -> 0; eMMC -> 1
eMMC has additional physical partitions such as *boot0,
*boot1 and others.
Use this attribute for unambiguous identification.
Print the type and name of the memory device in the message
to the user.
These patches are not needed for the kernel version 6.6 and later.
In addition, they cause minor harm when measuring temperature,
as they additionally calibrate the sensors.
Today, all the work is done by drivers/thermal/sun8i_thermal.c
Now the names of the patch files correspond to the entry
in the commit message.
Patches that have been transferred (copied) since time
immemorial and require revision have been removed.
No one wants to deal with them.
The bootinfo_emmc.bin file never changes.
The FSBL.bin file changes very rarely.
Using only coreutils, compare byte by byte the files
and the memory area in which they should be located.
If there is a match, then don't write anything down,
but just output a message.
Synchronization after each recording action.
Signed-off-by: The-going <48602507+The-going@users.noreply.github.com>
find the eMMC real mmcblk device numbered 0, 1, 2 and
inform the user about it in a message.
Item 6 of the selection menu will be visible if only
one device is found
* the existing patches for rk3308 audio codec have been disabled:
the rk3308 driver has been mainlined and thus the patches
don't apply anymore
* add the missing i2s_8ch_0 and _1 i2s nodes
* adjust "acodec" with "codec" device tree labels, to match
mainline kernel nomenclature
Establish some consistency with extension logging. Some extensions use another format:
display_alert "message" "${EXTENSION}" "info"
These were *not* adapted to this new schema.
Some of our scripts download tools from a repo. These can't be bumped by dependabot, so this workflow is a self-created dependabot to bump versions of those tools to stay up-to-date.
This workflow only creates a PR if the version was actually updated.
Tools currently supported:
- Shellcheck (in 2 different files)
- Shellfmt
- oci-oras
- Bat
Legacy: use TAG instead of BRANCH (gives us more control)
Current: update DTS files
Current: add needed patches up to v1.0.8
Fixup bluetooth node and disable by default (half broke anyway)
Misc fixups to bananapif3.wip and spacemit.conf file
Signed-off-by: Patrick Yavitz <pyavitz@armbian.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>
Reverse commit 75317a0 since this is a special case.
Eliminate the real reason for the inability to boot the kernel.
Linux kernel hangs in early boot on 32-bit ARM platform,
when ftrace 4-byte "mcount" function call location for
"_raw_spin_unlock_irqrestore" function straddles icache lines.
The problem is present for (cross-compiler) GCC 10, 11, 12.
It does not happen when the kernel is compiled with GCC 9,
even when condition (1) is satisfied.
Detailed description:
https://forum.armbian.com/topic/41339-linux-image-legacy-sunxi2451-kernel-6192-is-broken-stuck-at-starting-kernel/?do=findComment&comment=196528
- **win**: notice how one can actually _spot_ revelevant changes now
- case in point, `1022-arm64-dts-rockchip-support-poweroff-on-rock-5a.patch` -- will drop it in separate commit
- pci enum in preboot; required for working m.2 when booting some older kernels
- this board has an overlay (DEFAULT_OVERLAYS="nanopi-r5s-leds") to drive the LEDs, disable armbian-led-state service
NB: This family only has one board (BananaPi R2) and has not been properly maintained in many years, so 'current' LTS kernel is enough.
No need for 'edge' kernel unless someone plans to step in as maintainer who bumps and tests it on every new kernel release.
- Adjust BananaPi R2 board config (board is mainlined)
- Remove legacy kernel patch folder and kernel config
- Remove unstable WiFi stuff
* 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
Revert 07b37f227c8daa27e68f57b1c691fab34a06731e commit
For the sunxi (armhf) architecture, this commit results in
an inability to load the kernel. It's actually a crutch
that can break everything tomorrow.
Therefore, freeze the kernel version for better times.
- 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
* tools: shellfmt: Beautify and add board configs to formatting list
* Format the whole code using `lib/tools/shellfmt.sh`
---------
Co-authored-by: Igor <igor@armbian.com>
This temporary workaround was only needed for tinkerboard and xt-q8l-v10 version 2022.04 U-Boot. The version has since bumped to 2024.07 and builds fine without this.
* 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
- both artifacts use functions in the bsp/utils-bsp.sh file, which wasn't being hashed
- bsp-cli hashed non-existent 'packages/bsp-cli' directory, remove
- bsp-cli: be verbose when rsync'ing `packages/bsp/common`
- force sync in a few strategic spots
- utils-bsp.sh: be verbose when copying files (incl `config/optional` stuff)
This fixes detection of the config option for SpacemiT K1 which is `CONFIG_SOC_SPACEMIT_K1X`.
Otherwise it would not find it because it includes a '1'.
This gets compiled into the kernel and embedded in the initramfs.
It will also be available on the finished img at /lib/firmware.
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
- this avoids trouble building certain older versions with binman
- as it tries to `os.path.join(os.getenv('HOME'), 'bin')` and gets a `None` and dies
- naming names: `tinkerboard` & `xt-q8l-v10` (BOARDFAMILY=rockchip), which _actually use_ binman & 22.04 combo
As per `config/sources/families/include/meson64_common.inc`, the meson64 family is only using kernels 6.1, 6.6 and 6.9.
The kernel patch folder for 5.10 was forgotten to delete when the kernel was bumped.
As per `config/sources/families/include/rockchip64_common.inc`, the rockchip64 family is only using kernels 6.6 and 6.9.
The kernel patch folder for 6.1 was forgotten to delete when the kernel was bumped.
As per `config/sources/families/rockchip.conf`, the rockchip family is only using kernels 6.6 and 6.9.
The following kernel patch folders from old kernels are not used anymore:
- 4.4
- 5.10
- 5.15
- 6.1
BOARDFAMILY `rk322x` was integrated into the `rockchip` BOARDFAMILY in https://github.com/armbian/build/pull/6092
This integration made the hardware optimization for rk322x not apply anymore.
Also remove a rk322x optimization for an old 4.4 kernel
The board config file was likely copy-pasted from a former `media` board and thus includes some stuff that is not needed, like the abandoned U-Boot repo which is basically an old fork from Raxda's vendor U-Boot.
- Switch to default rk3588 vendor U-Boot (using a generic rk3588 defconfig)
- Cleanup board config file
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
Also move the ROCK_USB variable for RK3588 from rk3588.conf to rockchip64.conf to achieve consistency.
Remove the now obsolete variable for OrangePi 3B
Changes to be committed:
modified: config/boards/aml-s9xx-box.tvb
modified: packages/bsp/aml-s9xx-box/boot/extlinux/extlinux.conf.template
The aml-s9xx-box builds use the native TV Box u-boot. I've had as a
todo item to figure out how to not build and include an unused u-boot.
In a recent PR for a different board the opposite was being done
(adding a u-boot where a board didn't previously ship one), thus
I then had the info to remove it here.
This also changes the generated extlinux.conf to include a fdt line
by adding the boot_fdt_file to the board config file. This reduces
the effort needed to manually modify the extlinux.conf.
- otherwise:
```
fsck.ext4 -a -C0 /dev/mmcblk0p1
/dev/mmcblk0p1 has unsupported feature(s): FEATURE_C12
e2fsck: Get a newer version of e2fsck!
```
- `orphan_file` can only be disabled on recent-enough e2fsprogs, thus check version and compare
- in practice:
- boards that didn't specify their own blobs: bump DDR 1.08->1.16 ; BL31 1.28 -> 1.45 (example: rock-5b!)
- boards that specified 1.16/1.45 individually now follow the defaults (no change)
- boards that specified a different version: no change; just a TODO suggesting review/removal/go-with-the-defaults
- Mekotronics boards: bump from 1.11/1.38 to defaults (1.16 / 1.45)
The "swapaccount=" option has been deprecated in 6.1. Disable it in almost all boot scripts except "boot-sun50iw9.cmd" since that one is used in sun50iw9 legacy kernel, which is version 4.9.
Link to kernel commit:
b25806dcd3
Instead of having to add every new release to the list that does not support python2, inverse this if statement and only check if the build host is Debian bullseye or ubuntu jammy. Every release newer than those do not have python2. Older build hosts are unsupported.
Different build hosts have vastly different versions of setuptools and pyelftools depending on the host OS, e.g. Ubuntu 22.04 has setuptools v59 while the latest version at the time of this commit is setuptools v71.
Using Pip instead of APT to download these packages assures that all build hosts use the same version, removing some points of failures and inconsistencies.
Changes to be committed:
modified: aml-s9xx-box.tvb
PR #6659 broke upgrades for the aml-s9xx-box package. That PR introduced
two new files in /boot which is a fat filesystem on this box. The
standard package upgrade fails on a fat filesystem when files already
exist. PR #6659 failed to add the files to the remove list. This
PR does that.
If we want to check if a file is not from one of the listed folders, it needs to be check that
"NOT x AND NOT y AND NOT z" is true, instead of
"NOT x OR NOT y OR NOT z"
Validates the dts/dtb file for the selected board and outputs the validation logs to the user.
This can be used when adding a new board, developing or improving a dts file. Should lead to higher quality device trees and patches overall, if used.
Will show warnings/errors if patches patch in some functionalities to a devicetree file without patching in the dt-bindings .yaml at the same time.
- `NETWORKING_STACK` can be set to `none` (in config phase, pre-extensions) to not-add any networking extensions
- keep defaulting to systemd-networkd if BUILD_MINIMAL and NetworkManager otherwise
- fix typo in extension name
- add `NETWORKING_STACK` to change-tracking
- Use resolved no matter what manages the network (networkd or NetworkManager)
- Use resolved.conf.d/ directory to set DNS as recommended by resolved itself
- In armbian-firstrun, remove config specific to mvebu64|mt7623 since this is now done by default
Trying to run this in the background does not work correctly in its current iteration, setting the correct place on the screen for displaying did not work out.
Includes minor fixes and wording improvements.
This variable was originally introduces for the board "Espressobin" (mvebu64): 38db0b55f9
Use a hook in the mvebu64 and mt7623 family config to set ignored devices for NetworkManager instead.
- Rename extensions with "net-*" prefix
- Put the extensions into their own folder
- Split off time sync packages into their own extensions to be able to be used separately
- Put their config files into directories instead of using inline `cat <<- EOF >`
- Move some other NetworkManager related stuff into the extension
- Remove unneeded steps
- Install iproute2 by default on all images (for the `ip` command)
- use Chrony with Network Manager
- use timesync with systemd-networkd
- use NetPlan with Network manager only
- move command-not-found to CLI image only
- improve firstlogin ip detection
Firmware package was incorrectly marked as machine dependent.
This was fixed in radxa-pkg/aic8800#12, causing the file name to change.
Signed-off-by: ZHANG Yuntian <yt@radxa.com>
Shellcheck errors/warnings were:
In lib/functions/rootfs/distro-agnostic.sh line 155:
display_alert "Adding to extlinux.conf" "fdtoverlays=${DEFAULT_OVERLAYS[@]}" "debug"
^--------------------^ SC2145 (error): Argument mixes string and array. Use * or separate argument.
In lib/functions/rootfs/distro-agnostic.sh line 156:
echo " fdtoverlays ${DEFAULT_OVERLAYS[@]}" >> "$SDCARD/boot/extlinux/extlinux.conf"
^--------------------^ SC2145 (error): Argument mixes string and array. Use * or separate argument.
In lib/functions/rootfs/distro-agnostic.sh line 193:
if [[ -n $DEFAULT_OVERLAYS && -f "${SDCARD}"/boot/armbianEnv.txt ]]; then
^---------------^ SC2128 (warning): Expanding an array without an index only gives the first element.
Add a patch series to support VEPU121/VPU121, which mainly enables hardware decoding for H.264.
It can also decode MPEG2 and VP8 as well as do JPEG encoding.
Move kernel patch folder to archive/rockchip-rk3588-${KERNEL_MAJOR_MINOR} which is the default.
Also rename kernel config to linux-rockchip-rk3588-${KERNEL_MAJOR_MINOR}
Since the `edge` kernel branch often uses RC kernels, introduce a more stable `current` branch.
This branch should not be RC kernels and it also should move to an LTS kernel once released.
Patches are from the Linux Rockchip Mailing List, submitted by Alexey
Charkov. [1]
Notable improvements from changelog:
- Moved the TSADC enablement to per-board .dts/.dtsi files
- Dropped extra "inefficient" OPPs (same voltage - lower frequencies)
- Dropped second passive cooling trips altogether to keep things simple
- Added a cooling map for passive GPU cooling (in a separate patch)
- Added regulator coupling for EVB1 and QuartzPro64
Also enable automatic fan control on Rock 5B.
[1] https://lore.kernel.org/linux-rockchip/20240506-rk-dts-additions-v4-0-271023ddfd40@gmail.com/
"general-add-overlay-compilation-support.patch" became obsolete in
Linux 6.9 (see AR-2352 [1]). Fix this problem:
- Rename *.dts sources in overlay directory to *.dtso
- Change "target +=" line to "dts-y +=" in overlay Makefile
- Remove "always +=" line in overlay Makefile
- Add .scr compilation support in kernel scripts/Makefile.lib
- Patch kernel scripts/Makefile.dtbinst to avoid flattening overlay
directory
For the last two points, see
general-add-overlay-compilation-support.patch
Credits for this fix go to @paolosabatino
[1] https://armbian.atlassian.net/browse/AR-2352
- Bump mainline kernel from 6.10-rc1 to 6.10-rc2
- Remove patches which are now mainlined
- Re-number "fix-initial-PERST-GPIO-value" patch as per number
ordering seen in 0000.patching_config.yaml
- Rewrite kernel config
- `common_defaults_for_mainline` already sets KERNELPATCHDIR='archive/s5p6818-4.14' thus this symlink is not necessary
- 1 step closer to a clean `patch/kernel` dir, when we could finally get rid of `archive/`
The PR build workflow does not need to be started every time a single
reviwer is added, since requesting a review does not change the build.
If the 'Build' label was already added earlier, the build workflow will
have been started already.
On every PR, a workflow is started to check if artifacts should be
built. This happens not only once, but many times, e.g. for every
selected reviewer. Since the workflow has `cancel-in-progress`
enabled, workflows are started and immediately cancelled by the
next one, resulting in many notifications.
Move the `cancel-in-progress` concurrency policy to the second job
which starts only after a check is done if the 'Build' label is even
active on the PR. This should greatly reduce "Workflow cancelled"
notifications via GitHub and email (if enabled by the user).
Also make wording more clear.
- 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
- exclusive for edge / Kwiboo:
- enable UMS / RockUSB and other gadget stuff
- enable TCP networking features, wget etc
- enable EFI debugging stuff
- store environment in SPI
- uses preboot to flash led briefly
- this code pattern is becoming copypasta fast and needs refactor before it spreads too much
- also for all branches (legacy/vendor/edge):
- nanopct6: updated blobs to DDR v1.16 and BL31 v1.45
- `git format-patch --zero-commit` doesn't affect `index xxx...yyy` lines, only `From: `
- so use the _classy_ "use a regex with a callback" solution as git format-patch doesn't offer one
- this will make _all_ patches change when rewritten, but hopefully _for the last time_ !
- we need to preserve `index 000000000000..xxx` as zeros, which indicate new file creation, thus:
- new file creations are rewritten as `index 000000000000..111111111111`
- non-creations are rewritten as `index 111111111111..222222222222`
- this is the final version of #6455
* rename .dts sources in overlay directory as *.dtso
* change "target +=" line in "dts-y +=" in overlay Makefile
* remove "always +=" line in overlay Makefile
* add .scr compilation support in kernel scripts/Makefile.lib
* patch kernel scripts/Makefile.dtbinst to avoid flattening overlay
directory
for the last two points, see
general-add-overlay-compilation-support.patch
- 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
doas is not compatible with sudo flags. The codebase was checked for
sudo-specific uses of this function, but none were found, all cases were
in the form of `sudo <command>`. Replacing it with `doas <command>`
yields the same result.
doas is not compatible with sudo flags. The codebase was checked for
sudo-specific uses of this function, but none were found, all cases were
in the form of `sudo <command>`. Replacing it with `doas <command>`
yields the same result.
- I had worked this before AF sent his oneliner, but I forgot to PR
- Should be the same, except avoids sadness when trying with the wrong kernel/branch
- in preparation for tightening the shellcheck severity level
- it needs to be able to follow all sources; dynamic ones are ignored, static ones need root-relative prefix
create new boot script free of G12 stuff, using default u-boot load addresses.
La Frite boots from USB as well as eMMC, add ability to get root device via PARTUUID
* reload-or-restart ssh prevents botching if sshd is started by a systemd socket
* restart ssh prevents botching if sshd is started by a systemd socket
* move sshd activation from ssh.service to ssh.socket:
- more realiable, avoids possible race condition on first boot
- supplementary to PR#6586 - and commits ffee50a8a6 and 6725032191
* Add display_alert explaining the change in SSH activation
Ethernet is supposedly broken by design.
While Xunlong is working on a hw revision of this board it is to be expected that it will be released under the same name which will then ultimately contribute to users confusion why on some boards eth works and on others not. Therefore get rid of this one altogether.
- we had `_DEBUG=n` forced, which conflicted with `_EXPERT=y`;
- some important SBC features (like _GPIO_SYSFS) depend on _EXPERT=y
- we've plans to enable BTF/CO-RE kernels soon, so removing the non-debug enforcement makes some sense
- also, .config's will be free to determine debug config, nothing's changing in those here
- remove the `_EMBEDDED` special case handling, we can do that as well now
- add a separate hook to renable `CONFIG_GPIO_SYSFS=y`; it was a victim of `EXPERT=n` in some kernels
- this does not include rewrites of all the .configs -- those should be done in a separate batch -- either way effect is the same, hooks will always override .config's
- during rewrites, a large number of new options will show up, since `_EXPERT=y` is used as dependency for many of Kernel's experimental-ish features
* Add initial support for the Orange Pi 5 Pro
* Enable MotorComm network driver in rk35xx legacy and vendor kernel config
* Resolve conflicts
---------
Co-authored-by: Igor Pecovnik <igor@armbian.com>
- armhf was disabled for some releases and now we get spurious failures building certain artifacts (firmware)
Signed-off-by: Ricardo Pardini <ricardo@pardini.net>
* Odroid C1 received some update
* Zero 3W is maintained by Radxa
* Rock5 itx will be platinum
* Plus version nobody mentioned - save some build resources
* Enabled rock5c
* Enable other two rock5
* Adjust testing targets
In PF6507 the use of cpufrequtils was removed and the functionality put into armbian-hardware-optimization
This commit removes the remaining now unused installs of the deprecated cpufrequtils package
Changes to be committed:
modified: config/cli/bullseye/main/packages
modified: config/cli/common/main/packages
modified: config/cli/jammy/main/packages
Ref: Debian Bug report logs - #1069787
Credit: Mark Hindley <leepen@debian.org>
The debian/tests/debian-testing autopkgtest has been broken on 64bit archs by
the t64 transition in trixie. Specifically the test includes gnupg as an
additional package. Gnupg depends on gpg-agent which depends on
libnpth0. However, in trixie, libnpth0 is now provided by libnpth0t64 which
debootstrap doesn't handle.
I suggest changing the test to include gpgv which avoids the t64 transition
whilst providing similar functional coverage.
- 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>
Validates the dts/dtb file for the selected board and outputs the validation logs to the user.
This can be used when adding a new board, developing or improving a dts file. Should lead to higher quality device trees and patches overall, if used.
With CONFIG_DMA_BOUNCE_UNALIGNED_KMALLOC enabled, the arm64 kernel still
allocates the default SWIOTLB buffer (64MB) even if ZONE_DMA is disabled
or all the RAM fits into this zone. However, this potentially wastes a
non-negligible amount of memory on platforms with little RAM.
Reduce the SWIOTLB size to 1MB per 1GB of RAM if only needed for
kmalloc() buffer bouncing.
With CONFIG_DMA_BOUNCE_UNALIGNED_KMALLOC enabled, the arm64 kernel still
allocates the default SWIOTLB buffer (64MB) even if ZONE_DMA is disabled
or all the RAM fits into this zone. However, this potentially wastes a
non-negligible amount of memory on platforms with little RAM.
Reduce the SWIOTLB size to 1MB per 1GB of RAM if only needed for
kmalloc() buffer bouncing.
Signed-off-by: Patrick Yavitz <pyavitz@armbian.com>
- Add &spi0, &i2c4, &i2c5 for the pin-conections (all disabled)
- Remove &spi1 since it's not available on the board
- vcc_3v3_sd_s0: remove unevaluated property flasgs"enable-active-low", it's unneeded since the default assumed is Active low (linux/Documentation/devicetree/bindings/regulator/fixed-regulator.yaml)
- analog-sound: remove unevaluated property "simple-audio-card,hp-pin-name"
- &sdhci: remove "max-frequency = <200000000>;" since this value already defined as default in rk3588s.dtsi
- Rename node "button@1" to "button-user"
- Move "status" property to bottom, even if disabled
- Improve comments
- don't ask me why this was in there, or why there are desktop pkgs being installed during debootstrap
- debootstrap has limited dep resolution capabilities, do this later with apt, not debootstrap
* Fixing packages dependencies and small optimisations
* Disable printer-driver-all as its missing from Trixie and disable not needed tools
* Remove more apps
One patch also fixes Combo PHY.
Many thanks goes to the geniuses Sebastian Reichel and Michal Tomek. Without their brainpower, PCIe bifurification on the RK3588, like the mode used by the CM3588, would still be broken.
Sorting the patches to group them by category:
000* for general patches
00** for SoC related patches
01** for GPU/HDMI related patches
08** for wireless patches
1*** for board patches
101* for Rock-5B, 1012* for Rock-5A and so on
- useful for `collabora` and other experimental kernels, we don't want to have to add it to each individual board's KERNEL_TARGES one by one
- but we don't want to allow typos in BRANCH to emit very strange unrelated errors
* main-config: fix: avoid errors when BRANCH contains a dash; convert to underscore
* rockchip64_common: shellfmt, no changes
* rockchip64_common: move SERIALCON defaulting logic to a (verbose) hook for flexibility
* config: allow to build BRANCHes not listed in KERNEL_TARGET as long as the config is valid
- useful for `collabora` and other experimental kernels, we don't want to have to add it to each individual board's KERNEL_TARGES one by one
- but we don't want to allow typos in BRANCH to emit very strange unrelated errors
* extensions: mesa-oibaf extension by @monkaBlyat - mainline mesa PPA for Ubuntu
- does nothing on Debian
* extensions: (v3) amazingfated-rk35xx, now `rk-multimedia-amazingfate` - panfork-free
- simply skips if not on Jammy
- deploys Chromium + Widevine if desktop
* rockchip-rk3588: introduce `vendor-boogie-panthor` experimental BRANCH/kernel
- original: https://github.com/hbiyik/linux-rockchip.git (branch `rk-6.1-rkr1-panthor-v6`)
- I picked the commits on top of clean armbian/linux-rockchip `6.1-rkr1` as of 2024-04-01
- At https://github.com/rpardini/armbian-linux-rockchip-rk3588/tree/armbian-rk-6.1-rkr1-plus-boogie-panthor-v6
- Diff: https://github.com/armbian/linux-rockchip/compare/rk-6.1-rkr1...rpardini:armbian-linux-rockchip-rk3588:armbian-rk-6.1-rkr1-plus-boogie-panthor-v6
- rockchip-rk3588: introduce `boogie-bsp` BRANCH
- rockchip-rk3588: copy linux-rk35xx-vendor.config into linux-rk35xx-boogie-bsp.config
- rockchip-rk3588: update linux-rk35xx-boogie-bsp.config, no changes
- rockchip-rk3588: linux-rk35xx-boogie-bsp.config: `CONFIG_DRM_PANTHOR=m`
- rockchip-rk3588: linux-rk35xx-boogie-bsp.config: convert to defconfig
- rockchip-rk3588: rename to `BRANCH=vendor-boogie-panthor` for "clarity" (lol)
- rockchip-rk3588: vendor-boogie-panthor: force SERIALCON, full firmware (for blob needed for panthor) & mesa-oibaf extension
- rockchip-rk3588: vendor-boogie-panthor: enable amazingfated-rk35xx extension sans-panfork
BPI-CM4
No change in functionality. Fixup adjustments.
BPI-M2S
The fan on the unit is constantly running. So lets set thermal
trip points and add the ability to control when we want it to
kick on. By default it is set to power on at 60*C.
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
* Bump meson64 edge from 6.7 to 6.8
Changes to be committed:
modified: config/sources/families/include/meson64_common.inc
renamed: patch/kernel/archive/meson64-6.7 -> patch/kernel/archive/meson64-6.8
modified: patch/kernel/archive/meson64-6.8/board-bananapi-cm4-cm4io-fixes.patch
modified: patch/kernel/archive/meson64-6.8/general-input-touchscreen-Add-D-WAV-Multitouch.patch
new file: patch/kernel/archive/meson64-6.8/kernel-6.8-tools-cgroup-makefile.patch
* updates from rewrite-kernel-patches
* updates from rewrite-kernel-config
Since `armbian_kernel_config` is "NOT for user consumption. Do NOT use this hook, this is internal to Armbian."
`custom_kernel_config` is able to overwrite previously set values.
- `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>
Disable CONFIG_EXPERT as well since DEBUG_KERNEL=y is a dependency for EXPERT=y, meaning DEBUG_KERNEL would be re-enabled automatically if EXPERT is enabled
Manually forcing kernel options with 'call_extensions_kernel_config()' can introduce missing dependencies or misconfigurations. This commit introduces a function which checks the config, re-establishes its sanity if necessary and outputs any changes to the user.
This also makes `./compile.sh kernel-config` (exiting without changes) and `./compile.sh rewrite-kernel-config` ouput the same config file. Previously, this was not the case.
GitHub job summaries do not support colored output, but the kernel hardening script is using colored output. Thus, the job summary in the Actions panel is littered with ugly characters. This commit replaces them with emojis to enhance visibility.
* Re-add functionality to create linux-libc-dev when building kernel packages.
* linux-libc-dev: append -${BRANCH}-${LINUXFAMILY} to package name and update control file
- This way we can safely include BOOT_SOC in /etc/armbian-release as done in the previous commit
- this will cause a rebuild of _all_ bsp-cli packages, even those for boards that don't define BOOT_SOC
- hopefully one day we will have BOOT_SOC ("What is the SoC?") defined for all boards
- for now, it will be empty for those that don't define it, which should be harmless
- RTW8723DS, RTW8723DU is unsupported/deprecated/obsolete by the author since kernel 6.7 in favor of RTW88, so deprecate it for kernel >=6.8
- RTL88x2cs specifically says in its repo: "USE RTW88 NOT THIS DRIVER", so deprecate in favor of RTW88, except for meson64 family
- move random RTL88x2cs hook specific for meson64 family in drivers_network.sh to their family config
Also add commit dates to make life prettier and easier
The following drivers have been updated with fixes for 6.8
- driver_rtl8811CU_rtl8821C
- driver_rtl88x2bu
- driver_rtl8811_rtl8812_rtl8814_rtl8821
The following drivers have been updated without specific 6.8 patches:
- driver_rtl8189ES (patches for 6.7, deleted two upstreamed patches)
- driver_rtl8189FS (patches for 6.7, deleted four upstreamed patches)
- add network-manager & pulseaudio settings
- add discover, otherwise there is a broken icon on the dock
- add vault/scdaemon for gpg wallet
- enable debugs in create_desktop_package.sh; disable old postinst pa hack
- Don't have pre-placed text in text boxes which have to be deleted each time (placeholder/light grey background text is still there)
- Add latest host systems
- Add optional checkbox if building on WSL2
- Small wording improvements/changes
- it prepares git, applies patches to git, and re-writes them back from git
- same as kernel, it does git archeology for mbox-less patches, etc
- `uboot-patches-to-git` alias is also added, but my guess is rewrite is more useful
- refactor a common config function for both kernel and uboot
- example invocation: `./compile.sh BOARD=xxxx BRANCH=edge rewrite-uboot-patches`
- Add exact commit in a comment if it ever breaks
- Kwiboo's tree contains the OPi3B commits, not yet in upstream;
- I tried to rebase onto upstream v2024.04-rc3, but failed with "unmet direct dependencies detected for SPL_OF_LIBFDT" & SPL_LIBGENERIC_SUPPORT
- I guess this is most of the u-boot's I've touched over the years; notable exception is the orangepi3b (patches live in Kwiboo's tree)
- this is in preparation for bumping versions, hopefully soon
- radxa-zero, radxa-zero2, khadas-vim3, khadas-vim3l: drop patches for old u-boot versions no longer used
- Previously, Kwiboo's U-Boot was used due to his RK3568 patches (https://github.com/Kwiboo/u-boot-rockchip.git)
- Mainline U-Boot 2024.1 has sufficient support for RK3568 merged
- Mainline U-Boot 2024.4 received some improvements for RK3568
rtw88_8821cu takes priority over the github driver, so this
shouldn't effect other units or usb dongles people use.
My reasoning is; The rtw88 driver for reasons yet unknown seems
to trigger usb fails more often than the github driver. If a
fail occurs it will introduce dmesg spam and upon reboot leave
the onboard wireless module undetectable.
Signed-off-by: Patrick Yavitz <pyavitz@xxxxx.com>
Co-authored-by: Patrick Yavitz <pyavitz@xxxxx.com>
- example: `./compile.sh BOARD=xxxxx BRANCH=edge kernel-dtb`
- outputs preprocessed DTS source for board in question to `output/`
- also outputs same preprocessed DTS source, ran through `dtc` with input and output DTS formats for "normalized" comparisions
- `inventory-boards-csv.py`: moar Python atrocities done to data; idea here is to output one line per board, with <<varies>> for fields that, well, vary (mainly across BRANCH'es)
- `inventory-boards` sets `TARGETS_FILE` to something that doesn't exist, so the `default-targets.yaml` is used (so same list for everyone, save for userpatched-boards)
rk322x has peripheral mode that is not working
really well, add various non-upstream patches
and timing adjustments that makes things a bit
more usable (mass storage and ethernet works,
uac isn't)
description:By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/armbian/build/blob/master/.github/CODE_OF_CONDUCT.md)
options:
- label:I agree to follow this project's Code of Conduct
description:Discuss and track progress for a task you're working on.
title:"[Task]: "
labels:["Task/To-Do"]
body:
- type:markdown
attributes:
value:|
Please use checkboxes for subtasks and link relevant PRs or issues for reference.
You can use title tags like _Task_, _Story_ or _Epic_ similar to Jira [like described in the docs](https://docs.armbian.com/Process_Managing_Workflow/).
A _Story_ or _Epic_ may reference other _Tasks_ (GitHub issues). This task will automatically be mirrored to [Jira](https://armbian.atlassian.net/browse/AR).
Make sure to update your progress in case anyone wants to help with a task so noone is doing duplicate work.
Add the label "_Discussion_" to get feedback on your task and "_Help needed_" if you would prefer to not work on this this alone.
- type:textarea
id:task-list
attributes:
label:Task description
description:|
Enter your task goals here. You can make use of the subtask checkboxes (add more or remove if necessary). Actively ask for feedback if you want it.
description:By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/armbian/build/blob/master/.github/CODE_OF_CONDUCT.md)
options:
- label:I agree to follow this project's Code of Conduct
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
_Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change._
[Jira](https://armbian.atlassian.net/jira) reference number [AR-9999]
# Documentation summary for feature / change
_Please delete this section if entry to main documentation is not needed._
If documentation entry is predicted, please provide key elements for further implementation [into main documentation](https://docs.armbian.com) and set label to "Needs Documentation". You are welcome to open a PR to documentation or you can leave following information for technical writer:
- [ ] short description (copy / paste of PR title)
- [ ] summary (description relevant for end users)
- [ ] example of usage (how to see this in function)
# How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.
_Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration._
- [ ] Test A
- [ ] Test B
# Checklist:
_Please delete options that are not relevant._
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] Any dependent changes have been merged and published in downstream modules
@@ -38,10 +38,14 @@ You need to get a valid token from our DevOps team to proceed.
`forked-helper.yml` workflow helper can help to run custom workflows on the forked repositories.
1.Set `ARMBIAN_SELF_DISPATCH_TOKEN` secret on your repository with `security_events` permissions.
2. Helper will dispatch `repository_dispatch` event `armbian` on `push`, `release`, `deployment`,
`pull_request` and `workflow_dispatch` events. All needed event details you can find in `client_payload`
property of the event.
1.Create a [fine-grained Personal Access Token (PAT)](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-fine-grained-personal-access-token) with the `repo` scope and store it as a secret. It needs the following permissions on the target repositories:
-`contents`: read & write
-`metadata`: read only (automatically selected when selecting the contents permission)
2. Create a secret named `ARMBIAN_SELF_DISPATCH_TOKEN` on your repository with `security_events` permissions. To do this, head to your forked repository, go to `Settings` on the top bar, select `Secrets and variables` and then `Actions`. From here you can create a new repository secret.
-`Name`: `ARMBIAN_SELF_DISPATCH_TOKEN`
-`Secret`: Paste your fine-grained Personal Access Token that you created in step 1 here
3. Helper will dispatch `repository_dispatch` event `armbian` on `push`, `release`, `deployment`,
`pull_request` and `workflow_dispatch` events. All needed event details you can find in `client_payload` property of the event.
4. Create empty default branch in forked repository
5. Create workflow with `repository_dispatch` in default branch.
:white_check_mark: **Merged** into [$GITHUB_REPOSITORY](<$GITHUB_SERVER_URL/$GITHUB_REPOSITORY>) by [$GITHUB_ACTOR](<$GITHUB_SERVER_URL/$GITHUB_ACTOR>) - \
[Link](<$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/commit/$GITHUB_SHA>): *$(git show -s --format=%s)*\"}" ${{ secrets.WEBHOOKURL }}
# Run kernel-hardening-checker for each kernel config file excluding RISC-V configs, since they are not supported yet.
# See https://github.com/a13xp0p0v/kernel-hardening-checker/issues/56
# sed explanation: 1) Put spaces in front of every line 2) replace colored output with emojis since GitHub Actions job summaries don't support colored output
run:|
for file in ${{ steps.changed-files.outputs.all_changed_files }}; do
if [[ "${file}" = config/kernel/*.config && ! $(head -n 10 "${file}" | grep -q "riscv") ]]; then
run-name:Update Tools in Scripts by @${{ github.actor }}
#
# Some of our scripts download tools from a repo. These can't be bumped by dependabot, so this workflow is a self-created dependabot to bump versions of those tools to stay up-to-date.
# This workflow only creates a PR if the version was actually updated.
# To add a new tool, it just needs to be added to the matrix below by filling out all the variables.
#
permissions:
contents:write
pull-requests:write
on:
workflow_dispatch:
schedule:
- cron:"42 3 16 * *"# Run monthly on the 16th day of the month at 03:42 AM (random value as to not overload GitHub)
jobs:
update-tool-version:
name:Update ${{ matrix.tool.REPO_NAME }} version
runs-on:ubuntu-latest
# Add new tools here, no need to add anything anywhere else.
# Only works for tools hosted on GitHub for now.
strategy:
matrix:
tool:
# Shellcheck
- USER_NAME:"koalaman"# GitHub user name
REPO_NAME:"shellcheck"# GitHub repo name
PROJECT_NAME:"koalaman/shellcheck"# This is always USER_NAME/REPO_NAME (like in the GitHub URL)
VAR_FILE:"lib/tools/shellcheck.sh"# Where the version variable of the tool is saved
VERSION_VAR:"SHELLCHECK_VERSION"# Version variable how it appears in the script
# Shellcheck #2
- USER_NAME:"koalaman"
REPO_NAME:"shellcheck"
PROJECT_NAME:"koalaman/shellcheck"
VAR_FILE:"lib/functions/general/shellcheck.sh"
VERSION_VAR:"SHELLCHECK_VERSION"
# Shellfmt
- USER_NAME:"mvdan"
REPO_NAME:"sh"
PROJECT_NAME:"mvdan/sh"
VAR_FILE:"lib/tools/shellfmt.sh"
VERSION_VAR:"SHELLFMT_VERSION"
# ORAS
- USER_NAME:"oras-project"
REPO_NAME:"oras"
PROJECT_NAME:"oras-project/oras"
VAR_FILE:"lib/functions/general/oci-oras.sh"
VERSION_VAR:"ORAS_VERSION"
# Bat
- USER_NAME:"sharkdp"
REPO_NAME:"bat"
PROJECT_NAME:"sharkdp/bat"
VAR_FILE:"lib/functions/general/bat-cat.sh"
VERSION_VAR:"BATCAT_VERSION"
steps:
- name:Checkout repository
uses:actions/checkout@v4
- name:Get current ${{ matrix.tool.PROJECT_NAME }} version
title:"Bump ${{ matrix.tool.PROJECT_NAME}} from ${{ steps.get-version-current.outputs.version_current }} to ${{ steps.get-version-latest.outputs.version_latest }} in `${{ matrix.tool.VAR_FILE}}`"
body:|
Bump [${{ matrix.tool.PROJECT_NAME}}](https://github.com/${{ matrix.tool.PROJECT_NAME }}) from ${{ steps.get-version-current.outputs.version_current }} to ${{ steps.get-version-latest.outputs.version_latest }} by bumping `${{ matrix.tool.VERSION_VAR}}` in `${{ matrix.tool.VAR_FILE}}`.
<details><summary><b>Release notes</b></summary>
<p><em>Sourced from <a href="https://github.com/${{ matrix.tool.PROJECT_NAME }}/releases">${{ matrix.tool.PROJECT_NAME }}'s releases</a>.
<br>Please note that this only shows the release notes for the latest release.</em></p>
- Follow [@armbian](https://twitter.com/armbian) on 𝕏 (formerly known as Twitter), [Fosstodon](https://fosstodon.org/@armbian) or [LinkedIn](https://www.linkedin.com/company/armbian).
- Follow [@armbian](https://twitter.com/armbian) on 𝕏 (formerly known as Twitter), <a rel="me" href="https://fosstodon.org/@armbian">Mastodon</a> or [LinkedIn](https://www.linkedin.com/company/armbian).
@@ -74,7 +74,8 @@ If you are unsure about the documentation then invoke `$ grep -r -A5 -B5 "BUILD_
- edge: Use edge kernel
- [branch]: Use specified [branch] kernel
- [none]: Exits with error
- **KERNEL_TEST_TARGET** ( comma-separated list of kernel releases or branches ): if test targets are different for testings (internal switch)
- **KERNEL_TEST_TARGET** ( comma-separated list of kernel releases or branches ): if test targets are different for testings. Also applies to build list generation. (internal switch)
- **KERNEL_UPGRADE_FREEZE** ( comma-separated list of kernels with versions obove which they stop updating, example: KERNEL_UPGRADE_FREEZE="vendor-rk35xx@24.8.1,current-rockchip-rk3588@24.8.2" )
- **FULL_DESKTOP** ( boolean ): defines whether to install desktop stack of applications such as office, thunderbird, etc..
BOARD_NAME="T95Z Plus" # (a q201 Chinese clone with internal amlogic ethernet 1gbit, complete with a chunk of metal inside to delay thermal throttling)
BOOT_FDT_FILE="amlogic/meson-gxm-t95z-plus.dtb" # From chewitt's patches
BOARDFAMILY="meson-gxl" # s912's are actually meson-gxm, no harm done.
BOOTPATCHDIR="v2024.04/board_t95z" # This has a 000.patching_config.yaml inside, to avoid null-patching, as only new files are added (defconfig/dts's)
# Use extlinux and u-boot-menu extension
declare -g SRC_EXTLINUX="yes"
declare -g SRC_CMDLINE="loglevel=7 splash=verbose console=ttyAML0,115200" # Those boards are serial-debug only; 'root=LABEL=armbi_root' ?
enable_extension "u-boot-menu" # this generates the extlinux.conf
# Use the blobs for not-exactly-matching SBCs which are also S912. Note: the VIM2 blobs expect DDR4 and fails with "DDR4 chl: Rank0+1 @ 1008MHz" last message.
function post_uboot_custom_postprocess__t95z_uboot() {
unset uboot_custom_postprocess write_uboot_platform write_uboot_platform_mtd # disable stuff from rockchip64_common; we're using binman here which does all the work already
# Just use the binman-provided u-boot-rockchip.bin, which is ready-to-go
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
