You would probably be better off just building a kernel with a standard config
as a starter. Then you will get the kernel source code in a subdirectory of
build/tmp/work-common. Copy that source code tree in a separate location.
Put your original config in the tree and ”make xxxx_defconfig”.
copy your .config file to xxxx_config (not xxxx_defconfig)
and create a linux-xlnx bbappend that adds this file to SRC_URI.
The bbappend will copy the file to ${WORKDIR} and from there your bbappend
should copy the file to ${S}/arch/arm64/configs.
You set KERNEL_DEFCONFIG = ”xxxx_defconfig” (or whatever it is called) in your
MACHINE file.
If you call it xxxx_defconfig, Yocto will abort with an error message, since it
does not understand what is going on.
Best Regards
Ulf Samuelsson
> 13 dec. 2022 kl. 21:01 skrev David Babich <[email protected]>:
>
>
> Hi I have a long standing project in which I used petalinux 2018.3 to setup
> my kernel configuration. I've now migrated to a full yocto build flow using
> the various meta-xilinx layers (on the honister branch). I'd like to take my
> old 4.14 .config file and use it as a starting point for the 5.16 kernel. I
> will then take the resulting .config and add it to my layer as a defconfig.
> The upgrade is usually done with `make oldconfig` and I believe with
> petalinux (at least 2018.3) there was an optional flag '--oldconfig`. Does
> anyone know of a way to use yocto to run menuconfig with an oldconfig so that
> I can quickly upgrade?
>
>
>
> Thanks
> -David
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5121):
https://lists.yoctoproject.org/g/meta-xilinx/message/5121
Mute This Topic: https://lists.yoctoproject.org/mt/95652617/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
