going

This is not a viable option.

Do you mean that we need to make a boot image by analogy and similarity, as well-known distributions such as openSUSE, ubuntu do?

This will be a fork that will return the code to the parent project https://github.com/armbian/build ? Or is it planned to be developed as an independent project based on this branch?

@hexzhen3x7 This is grand planning worthy of a great warrior. Let me be curious. Do you represent the interests of the manufacturer?

There's only one way. You need to write these overlays yourself. Then compile them and put them in the target folder of overlays. After that, they will appear for selection in the configurator window. After you test them and be sure that they are correct, you can call me @going and publish the sources of these overlays here and I will add them to the build system.

This is an error in the build script. The discussion is here: issues/7456

The patch is accepted in v6.12 drivers/of/property.c Many thanks from the author of megi

This feature is necessary for developers. I mean those people who really understand the kernel code and will be able to draw conclusions and steps when they see the trace message. These people will be able to add any functionality to the kernel and debug it on their own. P.S. Thank you for not asking why the kernel is not being built with debugging symbols.

PR: https://github.com/armbian/build/pull/7442

Subject: Fix broken allwinner,sram dependency on h616, h618 Or, at your discretion, indicate in another way that this is relevant for these processors

I will send this fix to the author of the original patch. We will wait for his opinion. P.S. @Sesse I remembered that this is relevant for h616 and h618 processors. Other users have informed me about the lack of a temperature interface on boards with these processors. With your permission, I will edit the message in the patch a little.

Did I understand correctly? Did you mean this patches.megous/of-property-fw_devlink-Support-allwinner-sram-links.patch? You can disable any patch by simply putting a minus sign at the beginning of a line in the series file: diff --git a/patch/kernel/archive/sunxi-6.11/series.conf b/patch/kernel/archive/sunxi-6.11/series.conf index 3eaf6617..3a2067e0 100644 --- a/patch/kernel/archive/sunxi-6.11/series.conf +++ b/patch/kernel/archive/sunxi-6.11/series.conf @@ -171,7 +171,7 @@ patches.megous/usb-gadget-Fix-dangling-pointer-in-netdev-private-data.patch patches.megous/mmc-dw-mmc-rockchip-fix-sdmmc-after-soft-reboot.patch patches.megous/Revert-drm-sun4i-lvds-Invert-the-LVDS-polarity.patch - patches.megous/of-property-fw_devlink-Support-allwinner-sram-links.patch +- patches.megous/of-property-fw_devlink-Support-allwinner-sram-links.patch patches.megous/arm64-dts-rockchip-rk356x-Fix-PCIe-register-map-and-ranges.patch patches.megous/Fix-intptr_t-typedef.patch patches.megous/mmc-sunxi-mmc-Remove-runtime-PM.patch without making any other changes to the build system. The best solution is to make changes on top of all applied patches. Make a git commit and extract it as a patch to the root directory with patches. This can be done directly in the build system. sesion (1) cat <<- EOF > "userpatches/config-test.conf" display_alert "Settings from" "config-test.conf file" "info" BOARD=bigtreetech-cb1 BRANCH=edge RELEASE=bookworm KERNEL_GIT=shallow # Enter your github credentials here so that we know the author and how to contact you. declare -g MAINTAINERMAIL="48602507+The-going@users.noreply.github.com" declare -g MAINTAINER="The-going" declare -g SYNC_CLOCK="no" EOF ./compile.sh test kernel-patch # The build system will apply all patches, commit and stop. # Don't do anything in this terminal session (1). # The script will print the path to the directory where you want to make changes. # You will need another session (2) in the terminal to access and act on the kernel repository. session (2): cd /path/to/kernel-worktree sudo su # Make changes to the file in any convenient editor. For example: nano README # write and exit the editor session (1) Press <ENTER> And you'll see something like this: ───────┬─────────────────────────────────────────────────────────────────────────────────────────────────────────────── │ File: /home/leo/armbian/output/patch/kernel-rockchip-rk3588-edge.patch ───────┼─────────────────────────────────────────────────────────────────────────────────────────────────────────────── 1 │ diff --git a/README b/README 2 │ index fd903645e..fa0d6844d 100644 3 │ --- a/README 4 │ +++ b/README 5 │ @@ -1,5 +1,5 @@ 6 │ -Linux kernel 7 │ -============ 8 │ +Linux kernel Armbian framework patching 9 │ +======================================= 10 │ 11 │ There are several guides for kernel developers and users. These guides can 12 │ be rendered in a number of formats, like HTML and PDF. Please read ───────┴─────────────────────────────────────────────────────────────────────────────────────────────────────────────── [🚸] Are you happy with this patch? [ Type 'yes' to accept, 'stop' to stop patching, or anything else to keep patching ] Enter yes The script will make the correct patch assign it a strange name that does not match the "Subject:" field and put it in the "output/patch/" folder. leo@noble-vm:~/armbian$ batcat /home/leo/armbian/output/patch/kernel-rockchip-rk3588-edge.patch ───────┬───────────────────────────────────────────────────────────────────────── │ File: /home/leo/armbian/output/patch/kernel-rockchip-rk3588-edge.patch ───────┼───────────────────────────────────────────────────────────────────────── 1 │ From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001 2 │ From: The-going <48602507+The-going@users.noreply.github.com> 3 │ Date: Mon, 4 Nov 2024 12:21:22 +0000 4 │ Subject: Patching kernel rockchip-rk3588 files README 5 │ 6 │ Signed-off-by: The-going <48602507+The-going@users.noreply.github.com> 7 │ --- 8 │ README | 4 ++-- 9 │ 1 file changed, 2 insertions(+), 2 deletions(-) 10 │ 11 │ diff --git a/README b/README 12 │ index fd903645e..fa0d6844d 100644 13 │ --- a/README 14 │ +++ b/README 15 │ @@ -1,7 +1,7 @@ 16 │ -Linux kernel 17 │ -============ 18 │ +Linux kernel Armbian framework patching 19 │ +======================================= 20 │ 21 │ There are several guides for kernel developers and users. These guides can 22 │ be rendered in a number of formats, like HTML and PDF. Please read 23 │ Documentation/admin-guide/README.rst first. 24 │ 25 │ -- 26 │ Created with Armbian build tools https://github.com/armbian/build 27 │ ───────┴────────────────────────────────────────────────────────────────────────────── This strange behavior can be circumvented. session (2) cd /path/to/kernel-worktree sudo su # Tell who you are directly to git. git config --global user.email "48602507+The-going@users.noreply.github.com" git config --global user.name "The-going" # Check the git settings. cat ~/.gitconfig # Make the necessary changes to the file and commit. # The main thing is to write a good explanation in the message to the commit about the changes made. # End the superuser session exit # If it's a single commit then just send the patch to the destination (regular user session): git format-patch --keep-subject --filename-max-length=75 --abbrev=12 -1 -o /home/user/path/to/armbian-build/patch/kernel/archive/sunxi-6.11/ # If the changes are significant and you need several commits, # the best solution is to make a separate series. # Create an empty patches.addons folder in the target directory TDIR="/home/user/path/to/armbian-build/patch/kernel/archive/sunxi-6.11/patches.addons" mkdir $TDIR # If 5 commits revision_runge="HEAD~5..HEAD" # run script mk_format_patch.sh /home/user/path/to/armbian-build/tools/mk_format_patch . $revision_runge $TDIR # Add a list of new patches to the series.conf file cat ${TDIR}/../series.addons >>${TDIR}/../series.conf I wrote it in such detail because other users will read it. @Sesse You have very successfully found this rotten apple. I express my deep gratitude for the work done. Please post a properly designed patch here and I will send it to the megous upstream project so that it can be reviewed and the names included in v6.12. With respect

Please understand me correctly. I only have an A64 processor. And I can only check the real work on it. For the rest, only compilation. When moving patches to a new version, something always breaks and the work of fixing it falls on someone else who has boards with one processor or another. I can only give you hints.

In order to make it easier to view and analyze the source code, I support the kernel with patches already applied. Try to compare it with others sun50i-h616 trips It definitely works. sun50i-a64 trips

Try rolling back the build system to this commit: 90637986eef70e5478105b64039a8ba1bfd85062 All subsequent commits are irrelevant to sunxi. Check the correctness of the temperature triplet in the DTS, fix it and the sun8i_thermal temperature driver will work correctly.