From: Oleksii Kurochko <oleksii.kurochko@gmail.com>
To: Trevor Woerner <twoerner@gmail.com>,
yocto-patches@lists.yoctoproject.org
Subject: Re: [PATCH 3/3] radxa-zero-3: switch to yocto-dev kernel
Date: Sun, 15 Dec 2024 16:10:51 +0100 [thread overview]
Message-ID: <ef1b59d8-a018-44fc-8f0c-e58db58380d9@gmail.com> (raw)
In-Reply-To: <20241212195718.25203-3-twoerner@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4530 bytes --]
Hello Trevor,
On 12/12/24 8:57 PM, Trevor Woerner wrote:
> The radxa-zero-3{e|w} devices are not supported in the current yocto kernel,
> but they are supported in the yocto-dev kernel. Switch to yocto-dev until
> support is available in the yocto kernel.
>
> Reported-by: Oleksii Kurochko<oleksii.kurochko@gmail.com>
> Signed-off-by: Trevor Woerner<twoerner@gmail.com>
> ---
> conf/machine/include/radxa-zero-3.inc | 2 +-
> ...xt_%.bbappend => linux-yocto-dev.bbappend} | 0
> .../linux/linux-torvalds-next_git.bb | 25 -------------------
> recipes-kernel/linux/linux-yocto-dev.bbappend | 2 ++
> 4 files changed, 3 insertions(+), 26 deletions(-)
> rename dynamic-layers/rk-rauc-demo/recipes-kernel/linux/{linux-torvalds-next_%.bbappend => linux-yocto-dev.bbappend} (100%)
> delete mode 100644 recipes-kernel/linux/linux-torvalds-next_git.bb
>
> diff --git a/conf/machine/include/radxa-zero-3.inc b/conf/machine/include/radxa-zero-3.inc
> index 1c6f972c1e31..b351afae8c0f 100644
> --- a/conf/machine/include/radxa-zero-3.inc
> +++ b/conf/machine/include/radxa-zero-3.inc
> @@ -2,7 +2,7 @@ MACHINEOVERRIDES =. "radxa-zero-3:"
>
> require conf/machine/include/rk3566.inc
>
> -PREFERRED_PROVIDER_virtual/kernel = "linux-torvalds-next"
> +PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-dev"
> MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
>
> UBOOT_MACHINE = "radxa-zero-3-rk3566_defconfig"
> diff --git a/dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend b/dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-yocto-dev.bbappend
> similarity index 100%
> rename from dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-torvalds-next_%.bbappend
> rename to dynamic-layers/rk-rauc-demo/recipes-kernel/linux/linux-yocto-dev.bbappend
> diff --git a/recipes-kernel/linux/linux-torvalds-next_git.bb b/recipes-kernel/linux/linux-torvalds-next_git.bb
> deleted file mode 100644
> index b961b1408f09..000000000000
> --- a/recipes-kernel/linux/linux-torvalds-next_git.bb
> +++ /dev/null
> @@ -1,25 +0,0 @@
> -FILESEXTRAPATHS:prepend := "${THISDIR}/linux-yocto-dev:"
> -
> -DESCRIPTION = "Linux Kernel"
> -SECTION = "kernel"
> -LICENSE = "GPL-2.0-only"
> -LIC_FILES_CHKSUM ="file://COPYING;md5=6bc538ed5bd9a7fc9398086aedcd7e46"
> -
> -ERROR_QA:remove = "buildpaths"
> -DEFAULT_PREFERENCE = "-1"
> -COMPATIBLE_MACHINE = "^$"
> -COMPATIBLE_MACHINE:radxa-zero-3 = "radxa-zero-3"
> -
> -LINUX_VERSION = "6.11-rc6"
> -KERNEL_VERSION_SANITY_SKIP = "1"
> -PV = "${LINUX_VERSION}+git${SRCPV}"
> -SRC_URI = " \
> - git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git;protocol=https;nobranch=1 \
> - file://rockchip-kmeta;type=kmeta;name=rockchip-kmeta;destsuffix=rockchip-kmeta \
> - "
> -# this is tag 'next-20240904'
> -SRCREV = "fdadd93817f124fd0ea6ef251d4a1068b7feceba"
> -
> -inherit kernel
> -inherit kernel-yocto
> -require recipes-kernel/linux/linux-yocto.inc
> diff --git a/recipes-kernel/linux/linux-yocto-dev.bbappend b/recipes-kernel/linux/linux-yocto-dev.bbappend
> index b6a63d7b7b29..f738d1357d6c 100644
> --- a/recipes-kernel/linux/linux-yocto-dev.bbappend
> +++ b/recipes-kernel/linux/linux-yocto-dev.bbappend
> @@ -1,5 +1,7 @@
> FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
>
> COMPATIBLE_MACHINE:orangepi-5-plus = "orangepi-5-plus"
> +COMPATIBLE_MACHINE:radxa-zero-3 = "radxa-zero-3"
>
> SRC_URI:append:orangepi-5-plus ="
> file://rockchip-kmeta;type=kmeta;name=rockchip-kmeta;destsuffix=rockchip-kmeta"
> +SRC_URI:append:radxa-zero-3 = "file://rockchip-kmeta;ty
After applying of this patch series I see the following compilation
issue for kernel:
| ERROR: modpost: vmlinux: local symbol 'security_path_rmdir' was
exported
| make[2]: ***
[/home/ok/Projects/yocto/build/tmp/work-shared/radxa-zero-3e/kernel-source/scripts/Makefile.modpost:145:
vmlinux.symvers] Error 1
| make[1]: ***
[/home/ok/Projects/yocto/build/tmp/work-shared/radxa-zero-3e/kernel-source/Makefile:1871:
modpost] Error 2
| make: ***
[/home/ok/Projects/yocto/build/tmp/work-shared/radxa-zero-3e/kernel-source/Makefile:240:
__sub-make] Error 2
Should I apply something except the patches from these patch series?
Otherwise I think we should disable some security things ( as a
workaround ):
CONFIG_SECURITYFS=n CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_NETWORK_XFRM=n CONFIG_SECURITY_PATH=y
CONFIG_SECURITY_LANDLOCK=y
Best regards,
Oleksii
> pe=kmeta;name=rockchip-kmeta;destsuffix=rockchip-kmeta"
[-- Attachment #2: Type: text/html, Size: 6372 bytes --]
next prev parent reply other threads:[~2024-12-15 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 19:57 [PATCH 1/3] u-boot: switch to upstream SRCREV for rk-u-boot-env Trevor Woerner
2024-12-12 19:57 ` [PATCH 2/3] u-boot: use upstream for radxa-zero-3{e|w} Trevor Woerner
2024-12-15 14:49 ` Oleksii Kurochko
2024-12-15 14:59 ` Oleksii Kurochko
[not found] ` <181161B988FC6012.23577@lists.yoctoproject.org>
2024-12-15 15:15 ` [yocto-patches] " Oleksii Kurochko
2024-12-15 16:08 ` Trevor Woerner
2024-12-16 4:12 ` Trevor Woerner
2024-12-12 19:57 ` [PATCH 3/3] radxa-zero-3: switch to yocto-dev kernel Trevor Woerner
2024-12-15 15:10 ` Oleksii Kurochko [this message]
2024-12-15 16:10 ` Trevor Woerner
2024-12-15 17:30 ` [yocto-patches] " Oleksii Kurochko
2024-12-16 4:09 ` Trevor Woerner
2024-12-16 4:00 ` [PATCH 1/3] u-boot: switch to upstream SRCREV for rk-u-boot-env Trevor Woerner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef1b59d8-a018-44fc-8f0c-e58db58380d9@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=twoerner@gmail.com \
--cc=yocto-patches@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.