[cip-dev] : isar-cip-core and cip-kernel-config

[cip-dev] : isar-cip-core and cip-kernel-config

[Gylstorff Quirin]

Hi all,

I am currently trying to have all targets in isar-cip-core running with 
the matching configuration from cip-kernel-config. For some targets 
there are missing config entries to boot Debian 10 e.g. [1].

Should I add these configuration directly to the matching defconfig in
cip-kernel-config or add new defconfig/snippets for isar-cip-core?

Currently I am adding them directly to the defconfigs as it is IHMO
more manageable as it avoid snippets/configs all over the place.

[1]: 
https://gitlab.com/Quirin.Gy/cip-kernel-config/-/commit/92979dba2e3c03a422b5b9e8f9c592db9ff43f30

-- 
Quirin Gylstorff

Siemens AG
Corporate Technology
Research in Digitalization and Automation
Smart Embedded Systems
CT RDA IOT SES-DE
Otto-Hahn-Ring 6
81739 Muenchen, Germany
Mobile: +49 173 3746683
mailto:quirin.gylstorff at siemens.com
www.siemens.com/ingenuityforlife

Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim 
Hagemann Snabe; Managing Board: Joe Kaeser, Chairman, President and 
Chief Executive Officer; Roland Busch, Lisa Davis, Klaus Helmrich, 
Cedrik Neike, Michael Sen, Ralf P. Thomas; Registered offices: Berlin 
and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 
12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322

Important notice: This e-mail and any attachment thereof contain 
corporate proprietary information. If you have received it by mistake, 
please notify us immediately by reply e-mail and delete this e-mail and 
its attachments from your system. Thank you.

Re: [cip-dev] : isar-cip-core and cip-kernel-config

[Chris Paterson]

Hello Quirin,

> From: Gylstorff Quirin <quirin.gylstorff@siemens.com>
> Sent: 18 February 2020 16:20
> 
> Hi all,
> 
> I am currently trying to have all targets in isar-cip-core running with
> the matching configuration from cip-kernel-config. For some targets
> there are missing config entries to boot Debian 10 e.g. [1].
> 
> Should I add these configuration directly to the matching defconfig in
> cip-kernel-config or add new defconfig/snippets for isar-cip-core?

Good question.

I think cip-kernel-config was created to help the CIP maintainers know what configurations etc. to support/maintain.
How will it affect the maintainers if we start adding config options that are only required for testing, rather then for SLTS support? (Or do we technically also need SLTS support for the 'test' config options?)

> 
> Currently I am adding them directly to the defconfigs as it is IHMO
> more manageable as it avoid snippets/configs all over the place.

Would another option be to have complete configurations for testing, rather than just the extra snippets?
It would mean we need to maintain two copies of mostly the same thing, but it'll make scripting easier and be clear what is for the Kernel maintainers and what is for testing.

Would it be possible to use the same 'testing' configurations/snippets for both deby and isar versions of cip-core?

Kind regards, Chris

> 
> [1]:
> https://gitlab.com/Quirin.Gy/cip-kernel-config/-
> /commit/92979dba2e3c03a422b5b9e8f9c592db9ff43f30
> 
> --
> Quirin Gylstorff
> 
> Siemens AG
> Corporate Technology
> Research in Digitalization and Automation
> Smart Embedded Systems
> CT RDA IOT SES-DE
> Otto-Hahn-Ring 6
> 81739 Muenchen, Germany
> Mobile: +49 173 3746683
> mailto:quirin.gylstorff@siemens.com
> www.siemens.com/ingenuityforlife
> 
> Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim
> Hagemann Snabe; Managing Board: Joe Kaeser, Chairman, President and
> Chief Executive Officer; Roland Busch, Lisa Davis, Klaus Helmrich,
> Cedrik Neike, Michael Sen, Ralf P. Thomas; Registered offices: Berlin
> and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB
> 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322
> 
> Important notice: This e-mail and any attachment thereof contain
> corporate proprietary information. If you have received it by mistake,
> please notify us immediately by reply e-mail and delete this e-mail and
> its attachments from your system. Thank you.
_______________________________________________
cip-dev mailing list
cip-dev@lists.cip-project.org
https://lists.cip-project.org/mailman/listinfo/cip-dev

Re: [cip-dev] isar-cip-core and cip-kernel-config

[Daniel Sangorrin]

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Good to know Jan, thanks for the update.

> -----Original Message-----
> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Jan Kiszka
> Sent: Tuesday, June 9, 2020 7:01 PM
> To: cip-dev <cip-dev@lists.cip-project.org>
> Subject: [cip-dev] isar-cip-core and cip-kernel-config
> 
> Hi all,
> 
> a quick follow-up from our cip-core meeting today:
> 
> isar-cip-core is already able to pull configs from cip-kernel-config. It
> does so for all machines where USE_CIP_KERNEL_CONFIG = "1", ie.
> hihope-rzg2m, iwg20m and simatic-ipc227e. So we "only" need to check the
> other targets and see how they can be migrated.
> 
> And we should remove the old defconfigs from isar-cip-core then (some
> could already go).
> 
> Jan
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4791): https://lists.cip-project.org/g/cip-dev/message/4791
Mute This Topic: https://lists.cip-project.org/mt/74770939/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-

[cip-dev] isar-cip-core and cip-kernel-config

[Jan Kiszka]

[-- Attachment #1: Type: text/plain, Size: 514 bytes --]

Hi all,

a quick follow-up from our cip-core meeting today:

isar-cip-core is already able to pull configs from cip-kernel-config. It
does so for all machines where USE_CIP_KERNEL_CONFIG = "1", ie.
hihope-rzg2m, iwg20m and simatic-ipc227e. So we "only" need to check the
other targets and see how they can be migrated.

And we should remove the old defconfigs from isar-cip-core then (some
could already go).

Jan

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

[-- Attachment #2: Type: text/plain, Size: 419 bytes --]

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#4788): https://lists.cip-project.org/g/cip-dev/message/4788
Mute This Topic: https://lists.cip-project.org/mt/74770939/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy  [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-