diff options
| -rw-r--r-- | meta/classes/kernel.bbclass | 16 |
1 files changed, 15 insertions, 1 deletions
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass index 2f1006ddf0..ddff2ddcd2 100644 --- a/meta/classes/kernel.bbclass +++ b/meta/classes/kernel.bbclass | |||
| @@ -415,9 +415,23 @@ kernel_do_install() { | |||
| 415 | # | 415 | # |
| 416 | install -d ${D}/${KERNEL_IMAGEDEST} | 416 | install -d ${D}/${KERNEL_IMAGEDEST} |
| 417 | install -d ${D}/boot | 417 | install -d ${D}/boot |
| 418 | |||
| 419 | # | ||
| 420 | # When including an initramfs bundle inside a FIT image, the fitImage is created after the install task | ||
| 421 | # by do_assemble_fitimage_initramfs. | ||
| 422 | # This happens after the generation of the initramfs bundle (done by do_bundle_initramfs). | ||
| 423 | # So, at the level of the install task we should not try to install the fitImage. fitImage is still not | ||
| 424 | # generated yet. | ||
| 425 | # After the generation of the fitImage, the deploy task copies the fitImage from the build directory to | ||
| 426 | # the deploy folder. | ||
| 427 | # | ||
| 428 | |||
| 418 | for imageType in ${KERNEL_IMAGETYPES} ; do | 429 | for imageType in ${KERNEL_IMAGETYPES} ; do |
| 419 | install -m 0644 ${KERNEL_OUTPUT_DIR}/$imageType ${D}/${KERNEL_IMAGEDEST}/$imageType-${KERNEL_VERSION} | 430 | if [ $imageType != "fitImage" ] || [ "${INITRAMFS_IMAGE_BUNDLE}" != "1" ] ; then |
| 431 | install -m 0644 ${KERNEL_OUTPUT_DIR}/$imageType ${D}/${KERNEL_IMAGEDEST}/$imageType-${KERNEL_VERSION} | ||
| 432 | fi | ||
| 420 | done | 433 | done |
| 434 | |||
| 421 | install -m 0644 System.map ${D}/boot/System.map-${KERNEL_VERSION} | 435 | install -m 0644 System.map ${D}/boot/System.map-${KERNEL_VERSION} |
| 422 | install -m 0644 .config ${D}/boot/config-${KERNEL_VERSION} | 436 | install -m 0644 .config ${D}/boot/config-${KERNEL_VERSION} |
| 423 | install -m 0644 vmlinux ${D}/boot/vmlinux-${KERNEL_VERSION} | 437 | install -m 0644 vmlinux ${D}/boot/vmlinux-${KERNEL_VERSION} |
