On Thu, Aug 17, 2023 at 10:23 AM Jon Mason <[email protected]> wrote:
>
> In Linux kernel commit 724ba6751532055db75992fc6ae21c3e322e94a7
> all arm arch device tree files were moved into vendor directories
> (similar to what was being done in arm64).  This is causing the
> following error when building for qemuarmv5 with linux-yocto-dev:
>
> | make[2]: *** No rule to make target 'arch/arm/boot/dts/versatile-pb.dtb'.  
> Stop.
>
> Correcting the location to add the vendor directory of "arm" addresses
> the issue (and is what is being done for arm64 machines already).
>

Acked-by: Brue Ashfield <[email protected]>

Looks good to me!

Bruce

> Signed-off-by: Jon Mason <[email protected]>
> ---
>  meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb 
> b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> index e695e2d83eac..fba603b0f2b8 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
> @@ -51,7 +51,7 @@ DEPENDS += "${@bb.utils.contains('PACKAGECONFIG', 
> 'dt-validation', '', 'python3-
>
>  COMPATIBLE_MACHINE = 
> "^(qemuarmv5|qemuarm|qemuarm64|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv32|qemuriscv64|qemuloongarch64)$"
>
> -KERNEL_DEVICETREE:qemuarmv5 = "versatile-pb.dtb"
> +KERNEL_DEVICETREE:qemuarmv5 = "arm/versatile-pb.dtb"
>
>  # Functionality flags
>  KERNEL_EXTRA_FEATURES ?= "features/netfilter/netfilter.scc 
> features/taskstats/taskstats.scc"
> --
> 2.30.2
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186322): 
https://lists.openembedded.org/g/openembedded-core/message/186322
Mute This Topic: https://lists.openembedded.org/mt/100801220/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to