linux/poky.git/meta/classes-recipe/kernel-fitimage.bbclass, branch nanbield

kernel-fitImage: Strip path component from dtb

2023-09-28T11:37:47+00:00

Machines that have added subdirectires to the KERNEL_DEVICETREE recently, such as arm32 boards that were moved under subdirectories in Linux 6.5, will have that subdirectory in the node name of the FIT. This breaks existing systems that select a configuration in u-boot by it's name. Strip off the directory component from the device tree to preserve compatibility. (From OE-Core rev: 941ba1a132bafa9c9be855fb91fec96d8b06299f) Signed-off-by: Joel Stanley Signed-off-by: Ninad Palsule Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

kernel-fitImage: add machine compatible to config section

2023-08-01T08:51:20+00:00

to allow bootloaders to select best matching configuration based on compatible string. (From OE-Core rev: f4c82fb6da89359679c52318a8ebab7295c233e8) Signed-off-by: Denis OSTERLAND-HEIM Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

kernel-fitimage: support 64 bits address

2023-05-04T11:46:14+00:00

The default value of address-cells is "1", so the generated "its" file only supports 32bits address for kernel FIT image. However, some platforms may want to support 64bits address of UBOOT_LOADADDRESS and UBOOT_ENTRYPOINT. Therefore, adds a variable to support both 64bits and 32bits address cells. By default, the address-cell is "1" which is used for 32bits load address. If users would like to use 64bits load address, users are able to set as following for "0x400000000" 64bits load address. 1. FIT_ADDRESS_CELLS = "2" 2. UBOOT_LOADADDRESS= "0x04 0x00000000" (From OE-Core rev: 8ce15c76c50d5d61524fea585d19989baefb5df2) Signed-off-by: Jamin Lin Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

kernel-fitimage: Fix the default dtb config check

2023-04-13T10:56:07+00:00

The current check for default dtb image checks if the file exists and is not empty but appends a slash to the path due to which the file is never found. It also doesn't replace slash in filename with _ as done when populating the DTB variable. A better way to check the existence of the device tree would be from the list of DTBs since this is used during compilation. (From OE-Core rev: e8e31e11b158837804d029e85f5f8ed3c219a4ea) Signed-off-by: Arslan Ahmad Signed-off-by: Luca Ceresoli Signed-off-by: Richard Purdie

kernel-fitimage: Allow user to select dtb when multiple dtb exists

2023-01-12T23:08:51+00:00

Allow user to select the default DTB for FIT image when multiple dtb's exists. From machine.conf or local.conf user can specify the default dtb for FIT image as shown below. FIT_CONF_DEFAULT_DTB = "board-default.dtb" Also fallback to avaialable dtb when FIT_CONF_DEFAULT_DTB doesn't exits or empty. (From OE-Core rev: 160f2c58d68a049a87ddc7aedb2055152ac6ff4e) Signed-off-by: Sandeep Gundlupet Raju Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

kernel-fitimage: Adjust order of dtb/dtbo files

2023-01-12T23:08:51+00:00

The dtb files must be before the dtbo files, otherwise the overlays may not be applied correctly. From Bruce Ashfield: We can split between dtbs and dtbos, they just need to be sorted for reproducibility reasons. Of course, this was only working by luck previously (before the sort), since it has always been gathering dtbs and dtbo's with find, depending on filesystem ordering for the order in the fitimage). (From OE-Core rev: bcb3c0272f6ab846c3232548df1e1182bcc67486) Signed-off-by: Sandeep Gundlupet Raju Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

Revert "kernel-fitimage: reduce dependency to the cpio"

2022-12-13T23:49:48+00:00

This reverts commit ef0d0734866505c1c6e0528a0423e7248afb3ff8. We can't do this since the initramfs needs to use DEPLOY_DIR_IMAGE which isnt ready until do_image_complete. Signed-off-by: Richard Purdie

kernel-fitimage: reduce dependency to the cpio

2022-12-13T23:31:40+00:00

In order to build a fitimage, we don't need the image to be "complete" but we need the cpio portion of it built since the cpio is what ends up inside the FIT. By reducing the dependency to `do_image_cpio` we are able to include an image's rootfs as the ramdisk for a FIT and then bundle that FIT into a larger SPI flash layout. (From OE-Core rev: ef0d0734866505c1c6e0528a0423e7248afb3ff8) Signed-off-by: Patrick Williams Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

kernel-fitimage: skip FDT section creation for applicable symlinks

2022-10-28T08:44:52+00:00

When building a FIT image with device trees, each device tree lands in a FIT section and is referenced by a FIT configuration node. FIT images however also allow referencing the same device tree from multiple configurations. This can be useful to reduce FIT image size while staying compatible with existing bootloaders. Allow kernel-fitimage.bbclass users to take advantage of this by mapping each symlink to a regular device tree included in the FIT to a configuration that references a common device tree section. (From OE-Core rev: 21e240da63239826f3ef50ceef40c9519e9030d8) Signed-off-by: Ahmad Fatoum Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

kernel-fitimage: mangle slashes to underscores as late as possible

2022-10-28T08:44:52+00:00

This introduces no functional change, but will come in handy in a later commit where a file lookup will have us using the device tree name. If we keep it like it's now, we will lose the information whether an underscore is an original underscore or a mangled slash. (From OE-Core rev: 8bea426ca59d17715a3b32f7e3caf3e4b6db5ce9) Signed-off-by: Ahmad Fatoum Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie