RE: Generic x86 kernel configration (RE: [isar-cip-core][PATCH] Add support Plat'Home OpenBlocks IoT VX2)

nobuhiro1.iwamatsu
2024-04-23T13:18:42Z

Hi Jan,

> This script will likely prioritize the choice of later-provided configs over those
> earlier listed. But we rather generally want that features enabled in one config
> are also enabled in the merged ones (superset).
> How could we achieve this? Probably most of the comments I would have on
> the ipc227e diff would relate to this.

I see. I think we need to check the configuration of each device to achieve that.
First I create a list of configs.

Best regards,
Nobuhiro

> -----Original Message-----
> From: Jan Kiszka <jan.kiszka@siemens.com>
> Sent: Friday, April 12, 2024 1:51 AM
> To: iwamatsu nobuhiro(岩松 信洋 ○ＤＩＴＣ□ＤＩＴ○ＯＳＴ)
> <nobuhiro1.iwamatsu@toshiba.co.jp>; schilling.benjamin@siemens.com;
> cip-dev@lists.cip-project.org
> Cc: Chris.Paterson2@renesas.com; minmin@plathome.co.jp
> Subject: Re: Generic x86 kernel configration (RE: [isar-cip-core][PATCH] Add
> support Plat'Home OpenBlocks IoT VX2)
>
> Hi Nobuhiro,
>
> thanks for picking this up!
>
> On 05.04.24 09:39, nobuhiro1.iwamatsu@toshiba.co.jp wrote:
> > Hi all,
> >
> > First of all I created generic kernel configuration for x86 CIP reference
> hardware and performed boot tests.
> > The configurations of each device in cip-kernel-config are merged using
> KERNEL/scripts/kconfig/merge_config.sh.
>
> This script will likely prioritize the choice of later-provided configs over those
> earlier listed. But we rather generally want that features enabled in one config
> are also enabled in the merged ones (superset).
> How could we achieve this? Probably most of the comments I would have on
> the ipc227e diff would relate to this.
>
> Jan
>
> > Also, booting is fine[2][3]. But there are a lot of differences in the
> > configurations[0][1], so I think we need to decide what to do with them.
> >
> > About M-COM x86, but I haven't investigated it yet.
> >
> > Best regards,
> > Nobuhiro
> >
> > Merged config:
> >
> > https://gitlab.com/iwamatsu/cip-merge-config-work/-/raw/master/config
> > Diff with ipc227e original config [0]:
> >
> >
> https://gitlab.com/iwamatsu/cip-merge-config-work/-/raw/master/siemens
> > _ipc227e_config.v6.1.83-cip18.diff
> > Diff with OpenBlocks IoT VX2 original config[1]:
> >
> >
> https://gitlab.com/iwamatsu/cip-merge-config-work/-/blob/master/platho
> > me_obsvx2_config.v6.1.83-cip18.diff
> > Kernel size:
> > 7760544 bytes
> >
> > ipc227e boot log (merged)[2]
> > https://lava.ciplatform.org/scheduler/job/1113259
> >
> >
> https://gitlab.com/iwamatsu/cip-merge-config-work/-/raw/master/ipc227e
> > -merged.log
> > ipc227e boot log (NO merged)
> > https://lava.ciplatform.org/scheduler/job/1113356
> >
> https://gitlab.com/iwamatsu/cip-merge-config-work/-/raw/master/ipc227e-
> NO-merged.log
> > kernel size: 7251072 bytes
> > ipc227e boot log (diff)
> >
> >
> https://gitlab.com/iwamatsu/cip-merge-config-work/-/blob/master/ipc227
> > e.log.diff
> >
> > OpenBlocks IoT VX2 boot log (merged)[3]
> > https://lava.ciplatform.org/scheduler/job/1113301
> >
> >
> https://gitlab.com/iwamatsu/cip-merge-config-work/-/raw/master/obs-mer
> > ged.log OpenBlocks IoT VX2 boot log (NO merged)
> > https://lava.ciplatform.org/scheduler/job/1113303
> >
> https://gitlab.com/iwamatsu/cip-merge-config-work/-/raw/master/obs-no-
> merge.log
> > kernel size: 9203296 bytes
> > OpenBlocks IoT VX2 boot log (diff)
> >
> >
> https://gitlab.com/iwamatsu/cip-merge-config-work/-/raw/master/obs.log
> > .diff
> >
> >
> >> -----Original Message-----
> >> From: Jan Kiszka <jan.kiszka@siemens.com>
> >> Sent: Tuesday, March 26, 2024 3:52 PM
> >> To: Benjamin Schilling <schilling.benjamin@siemens.com>;
> >> cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 ○ＤＩＴＣ□
> Ｄ
> >> ＩＴ○ＯＳＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>
> >> Subject: Re: [isar-cip-core][PATCH] Add support Plat'Home OpenBlocks
> >> IoT
> >> VX2
> >>
> >> On 22.03.24 12:39, Benjamin Schilling wrote:
> >>> Hi all,
> >>>
> >>> I'm joining the discussion to start integrating the M-COM x86 support.
> >>> What's the status on the generic x86-64 target?
> >>>
> >>
> >> Nobuhiro wrote recently he has a prototype. Maybe he can share to
> >> finalize it together.
> >>
> >> Jan
> >>
> >> --
> >> Siemens AG, Technology
> >> Linux Expert Center
>
> --
> Siemens AG, Technology
> Linux Expert Center