Re: [PATCH 10/10] meta-isar: add creator-ci40-marduk machine (mipsel + mainline kernel)

[Jan Kiszka <jan.kiszka@siemens.com>]

On 24.10.19 20:13, [ext] Henning Schild wrote:
> Am Thu, 24 Oct 2019 11:02:24 +0200
> schrieb Cedric Hombourger <Cedric_Hombourger@mentor.com>:
> 
>> Signed-off-by: Cedric Hombourger <Cedric_Hombourger@mentor.com>
>> ---
>>  .../creator-ci40-image-extension.bbclass      |  9 +++++++
>>  meta-isar/conf/local.conf.sample              |  1 +
>>  .../conf/machine/creator-ci40-marduk.conf     | 14 ++++++++++
>>  .../creator-ci40-marduk-buster.conf           |  7 +++++
>>  ...tachio-set-KBUILD_IMAGE-to-uImage.gz.patch | 27
>> +++++++++++++++++++ .../recipes-kernel/linux/files/no-display.cfg |
>> 1 + .../recipes-kernel/linux/files/no-fs-nfs.cfg  |  6 +++++
>>  .../recipes-kernel/linux/files/no-sound.cfg   |  1 +
>>  .../linux/linux-mainline_4.19.80.bb           |  6 +++++
>>  9 files changed, 72 insertions(+)
>>  create mode 100644
>> meta-isar/classes/creator-ci40-image-extension.bbclass create mode
>> 100644 meta-isar/conf/machine/creator-ci40-marduk.conf create mode
>> 100644 meta-isar/conf/multiconfig/creator-ci40-marduk-buster.conf
>> create mode 100644
>> meta-isar/recipes-kernel/linux/files/0001-MIPS-pistachio-set-KBUILD_IMAGE-to-uImage.gz.patch
>> create mode 100644
>> meta-isar/recipes-kernel/linux/files/no-display.cfg create mode
>> 100644 meta-isar/recipes-kernel/linux/files/no-fs-nfs.cfg create mode
>> 100644 meta-isar/recipes-kernel/linux/files/no-sound.cfg
>>
>> diff --git a/meta-isar/classes/creator-ci40-image-extension.bbclass
>> b/meta-isar/classes/creator-ci40-image-extension.bbclass new file
>> mode 100644 index 0000000..9879cd7
>> --- /dev/null
>> +++ b/meta-isar/classes/creator-ci40-image-extension.bbclass
>> @@ -0,0 +1,9 @@
>> +# This software is a part of ISAR.
>> +# Copyright (C) Mentor Graphics, a Siemens business, 2019
>> +
>> +ROOTFS_POSTPROCESS_COMMAND =+ "image_postprocess_creator_ci40"
>> +image_postprocess_creator_ci40() {
>> +    sudo mv ${IMAGE_ROOTFS}/boot/vmlinux-* ${IMAGE_ROOTFS}/uImage
>> +    sudo mv ${IMAGE_ROOTFS}/usr/lib/linux-*/img/*dtb ${IMAGE_ROOTFS}/
>> +    sudo rm -f ${IMAGE_ROOTFS}/vmlinux*
>> +}
> 
> And this is what you needed the hacky feature for. I understand but i
> guess is can be done with postinst. I think the symlinks in / are done
> by postinst scripts. And the final location is really only interesting
> for your bootloader, which should maybe look in /boot.
> 
> Moving these files around will cause an inconsistent view of your
> package manager on your rootfs. Copies to /usr/local/ would maybe be
> fine.

I suspect it relates to limitation of the U-Boot scripting on that
particular board, doesn't it? Better patched there then.

Jan

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux