Date   

Re: CIP Patchwork

Jan Kiszka
 

On 30.07.20 11:16, Nobuhiro Iwamatsu wrote:
Hi,

-----Original Message-----
From: Chris Paterson [mailto:Chris.Paterson2@renesas.com]
Sent: Thursday, July 23, 2020 6:37 PM
To: masashi.kudo@cybertrust.co.jp; iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT)
<nobuhiro1.iwamatsu@toshiba.co.jp>; pavel@denx.de; ben.hutchings@codethink.co.uk; SZ.Lin@moxa.com; wens@csie.org
Cc: cip-dev@lists.cip-project.org
Subject: CIP Patchwork

Hello all,

CIP has a Patchwork instance [0] that monitors the cip-dev mainline list for patches.

It doesn't look like it's particularly maintained, with most patches in the "new" state.
As a project, do we want to start maintaining Patchwork? Should we kill it off? Or just stick with the status-quo?

We briefly discussed this in the IRC meeting today, but I thought we should check with a wider audience before making
a decision.
Not all, I sometime checked and updated this.
There are more non-kernel patches, so I re-check this.
And I use this for patch tracking and patch appling.
Can we set filters based on common tags like "[isar-cip-core]" (which I just forgot to use)?

Jan



So, any thoughts?

[0] https://patchwork.kernel.org/project/cip-dev/list/

Kind regards, Chris
Best regards,
Nobuhiro
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


Re: [PATCH] kas: Pull common target out of board files

Jan Kiszka
 

Oops, should have been tagged with "isar-cip-core".

Jan

On 30.07.20 11:36, Jan Kiszka wrote:
From: Jan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
kas-cip.yml | 1 +
kas/board/bbb.yml | 1 -
kas/board/iwg20m.yml | 1 -
kas/board/qemu-amd64.yml | 1 -
kas/board/rzg2m.yml | 1 -
kas/board/simatic-ipc227e.yml | 1 -
6 files changed, 1 insertion(+), 5 deletions(-)
diff --git a/kas-cip.yml b/kas-cip.yml
index 0da07db..f4edd0f 100644
--- a/kas-cip.yml
+++ b/kas-cip.yml
@@ -13,6 +13,7 @@ header:
version: 8
distro: cip-core-buster
+target: cip-core-image
repos:
cip-core:
diff --git a/kas/board/bbb.yml b/kas/board/bbb.yml
index 08e9ec0..fc8dbbe 100644
--- a/kas/board/bbb.yml
+++ b/kas/board/bbb.yml
@@ -13,4 +13,3 @@ header:
version: 8
machine: bbb
-target: cip-core-image
diff --git a/kas/board/iwg20m.yml b/kas/board/iwg20m.yml
index fbb2a2e..3def3af 100644
--- a/kas/board/iwg20m.yml
+++ b/kas/board/iwg20m.yml
@@ -13,4 +13,3 @@ header:
version: 8
machine: iwg20m
-target: cip-core-image
diff --git a/kas/board/qemu-amd64.yml b/kas/board/qemu-amd64.yml
index 8b6a3ac..02e99ba 100644
--- a/kas/board/qemu-amd64.yml
+++ b/kas/board/qemu-amd64.yml
@@ -13,4 +13,3 @@ header:
version: 8
machine: qemu-amd64
-target: cip-core-image
diff --git a/kas/board/rzg2m.yml b/kas/board/rzg2m.yml
index f68c7b8..bbef122 100644
--- a/kas/board/rzg2m.yml
+++ b/kas/board/rzg2m.yml
@@ -13,4 +13,3 @@ header:
version: 8
machine: hihope-rzg2m
-target: cip-core-image
diff --git a/kas/board/simatic-ipc227e.yml b/kas/board/simatic-ipc227e.yml
index 25db755..a2c6965 100644
--- a/kas/board/simatic-ipc227e.yml
+++ b/kas/board/simatic-ipc227e.yml
@@ -13,4 +13,3 @@ header:
version: 8
machine: simatic-ipc227e
-target: cip-core-image
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


[PATCH] kas: Pull common target out of board files

Jan Kiszka
 

From: Jan Kiszka <jan.kiszka@siemens.com>

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
kas-cip.yml | 1 +
kas/board/bbb.yml | 1 -
kas/board/iwg20m.yml | 1 -
kas/board/qemu-amd64.yml | 1 -
kas/board/rzg2m.yml | 1 -
kas/board/simatic-ipc227e.yml | 1 -
6 files changed, 1 insertion(+), 5 deletions(-)

diff --git a/kas-cip.yml b/kas-cip.yml
index 0da07db..f4edd0f 100644
--- a/kas-cip.yml
+++ b/kas-cip.yml
@@ -13,6 +13,7 @@ header:
version: 8

distro: cip-core-buster
+target: cip-core-image

repos:
cip-core:
diff --git a/kas/board/bbb.yml b/kas/board/bbb.yml
index 08e9ec0..fc8dbbe 100644
--- a/kas/board/bbb.yml
+++ b/kas/board/bbb.yml
@@ -13,4 +13,3 @@ header:
version: 8

machine: bbb
-target: cip-core-image
diff --git a/kas/board/iwg20m.yml b/kas/board/iwg20m.yml
index fbb2a2e..3def3af 100644
--- a/kas/board/iwg20m.yml
+++ b/kas/board/iwg20m.yml
@@ -13,4 +13,3 @@ header:
version: 8

machine: iwg20m
-target: cip-core-image
diff --git a/kas/board/qemu-amd64.yml b/kas/board/qemu-amd64.yml
index 8b6a3ac..02e99ba 100644
--- a/kas/board/qemu-amd64.yml
+++ b/kas/board/qemu-amd64.yml
@@ -13,4 +13,3 @@ header:
version: 8

machine: qemu-amd64
-target: cip-core-image
diff --git a/kas/board/rzg2m.yml b/kas/board/rzg2m.yml
index f68c7b8..bbef122 100644
--- a/kas/board/rzg2m.yml
+++ b/kas/board/rzg2m.yml
@@ -13,4 +13,3 @@ header:
version: 8

machine: hihope-rzg2m
-target: cip-core-image
diff --git a/kas/board/simatic-ipc227e.yml b/kas/board/simatic-ipc227e.yml
index 25db755..a2c6965 100644
--- a/kas/board/simatic-ipc227e.yml
+++ b/kas/board/simatic-ipc227e.yml
@@ -13,4 +13,3 @@ header:
version: 8

machine: simatic-ipc227e
-target: cip-core-image
--
2.26.2


Re: [isar-cip-core] qemu-amd64: use cip-kernel-config file

Jan Kiszka
 

On 30.07.20 10:32, Daniel Sangorrin wrote:
We should use configs from the cip-kernel-config
repository, which are shared between CIP Core
reference implementations and CIP testing.
I updated the cip-kernel-config commit id because QEMU's
config file was inexistent.
I have built and boot-tested the QEMU target but not
the other ones. Hopefully our CI will detect any
regressions.
Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
---
conf/machine/qemu-amd64.conf | 2 +
.../linux/files/qemu-amd64_defconfig | 353 ------------------
recipes-kernel/linux/linux-cip-common.inc | 2 +-
3 files changed, 3 insertions(+), 354 deletions(-)
delete mode 100644 recipes-kernel/linux/files/qemu-amd64_defconfig
diff --git a/conf/machine/qemu-amd64.conf b/conf/machine/qemu-amd64.conf
index 7cbd55b..c90d957 100644
--- a/conf/machine/qemu-amd64.conf
+++ b/conf/machine/qemu-amd64.conf
@@ -9,3 +9,5 @@
DISTRO_ARCH = "amd64"
IMAGE_TYPE ?= "ext4-img"
+USE_CIP_KERNEL_CONFIG = "1"
+KERNEL_DEFCONFIG = "cip-kernel-config/4.19.y-cip/x86/cip_qemu_defconfig"
diff --git a/recipes-kernel/linux/files/qemu-amd64_defconfig b/recipes-kernel/linux/files/qemu-amd64_defconfig
deleted file mode 100644
index 7487152..0000000
--- a/recipes-kernel/linux/files/qemu-amd64_defconfig
+++ /dev/null
@@ -1,353 +0,0 @@
-# CONFIG_LOCALVERSION_AUTO is not set
-CONFIG_SYSVIPC=y
-CONFIG_POSIX_MQUEUE=y
-CONFIG_FHANDLE=y
-CONFIG_NO_HZ_IDLE=y
-CONFIG_HIGH_RES_TIMERS=y
-CONFIG_BSD_PROCESS_ACCT=y
-CONFIG_BSD_PROCESS_ACCT_V3=y
-CONFIG_TASKSTATS=y
-CONFIG_TASK_DELAY_ACCT=y
-CONFIG_TASK_XACCT=y
-CONFIG_TASK_IO_ACCOUNTING=y
-CONFIG_IKCONFIG=m
-CONFIG_NUMA_BALANCING=y
-# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
-CONFIG_CGROUP_FREEZER=y
-CONFIG_CGROUP_PIDS=y
-CONFIG_CGROUP_DEVICE=y
-CONFIG_CPUSETS=y
-CONFIG_CGROUP_CPUACCT=y
-CONFIG_MEMCG=y
-CONFIG_MEMCG_SWAP=y
-# CONFIG_MEMCG_SWAP_ENABLED is not set
-CONFIG_CGROUP_PERF=y
-CONFIG_CFS_BANDWIDTH=y
-CONFIG_BLK_CGROUP=y
-CONFIG_CHECKPOINT_RESTORE=y
-CONFIG_NAMESPACES=y
-CONFIG_USER_NS=y
-CONFIG_SCHED_AUTOGROUP=y
-CONFIG_BLK_DEV_INITRD=y
-CONFIG_EXPERT=y
-CONFIG_KALLSYMS_ALL=y
-CONFIG_BPF_SYSCALL=y
-CONFIG_USERFAULTFD=y
-# CONFIG_COMPAT_BRK is not set
-CONFIG_SLAB=y
-CONFIG_PROFILING=y
-CONFIG_KPROBES=y
-CONFIG_JUMP_LABEL=y
-CONFIG_CC_STACKPROTECTOR_STRONG=y
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-CONFIG_MODVERSIONS=y
-CONFIG_BLK_DEV_BSGLIB=y
-CONFIG_BLK_DEV_INTEGRITY=y
-CONFIG_BLK_DEV_THROTTLING=y
-CONFIG_PARTITION_ADVANCED=y
-CONFIG_CFQ_GROUP_IOSCHED=y
-CONFIG_SMP=y
-CONFIG_X86_X2APIC=y
-# CONFIG_X86_EXTENDED_PLATFORM is not set
-CONFIG_X86_INTEL_LPSS=y
-CONFIG_X86_AMD_PLATFORM_DEVICE=y
-CONFIG_IOSF_MBI=y
-CONFIG_HYPERVISOR_GUEST=y
-CONFIG_PARAVIRT=y
-CONFIG_PARAVIRT_SPINLOCKS=y
-CONFIG_GART_IOMMU=y
-CONFIG_CALGARY_IOMMU=y
-CONFIG_NR_CPUS=512
-CONFIG_SCHED_SMT=y
-CONFIG_PREEMPT_VOLUNTARY=y
-CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
-CONFIG_MICROCODE_AMD=y
-CONFIG_NUMA=y
-CONFIG_NUMA_EMU=y
-CONFIG_MEMORY_HOTPLUG=y
-CONFIG_MEMORY_HOTREMOVE=y
-CONFIG_KSM=y
-CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
-CONFIG_MEMORY_FAILURE=y
-CONFIG_TRANSPARENT_HUGEPAGE=y
-CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
-CONFIG_FRONTSWAP=y
-CONFIG_MEM_SOFT_DIRTY=y
-CONFIG_ZSWAP=y
-CONFIG_ZBUD=y
-CONFIG_X86_INTEL_MPX=y
-CONFIG_EFI=y
-CONFIG_EFI_STUB=y
-CONFIG_EFI_MIXED=y
-CONFIG_KEXEC=y
-CONFIG_KEXEC_FILE=y
-CONFIG_KEXEC_VERIFY_SIG=y
-CONFIG_CRASH_DUMP=y
-CONFIG_RANDOMIZE_BASE=y
-CONFIG_LIVEPATCH=y
-CONFIG_HIBERNATION=y
-CONFIG_PM_DEBUG=y
-CONFIG_PM_ADVANCED_DEBUG=y
-# CONFIG_ACPI_AC is not set
-# CONFIG_ACPI_BATTERY is not set
-CONFIG_ACPI_BUTTON=m
-# CONFIG_ACPI_FAN is not set
-CONFIG_ACPI_DOCK=y
-# CONFIG_ACPI_THERMAL is not set
-CONFIG_ACPI_PCI_SLOT=y
-CONFIG_ACPI_HOTPLUG_MEMORY=y
-CONFIG_ACPI_BGRT=y
-CONFIG_ACPI_APEI=y
-CONFIG_ACPI_APEI_GHES=y
-CONFIG_ACPI_APEI_PCIEAER=y
-CONFIG_ACPI_APEI_MEMORY_FAILURE=y
-CONFIG_ACPI_EXTLOG=y
-CONFIG_SFI=y
-CONFIG_CPU_FREQ=y
-CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
-CONFIG_X86_INTEL_PSTATE=y
-CONFIG_INTEL_IDLE=y
-CONFIG_PCI_MMCONFIG=y
-CONFIG_PCIEPORTBUS=y
-CONFIG_HOTPLUG_PCI_PCIE=y
-CONFIG_PCI_REALLOC_ENABLE_AUTO=y
-CONFIG_PCI_IOV=y
-CONFIG_HOTPLUG_PCI=y
-CONFIG_HOTPLUG_PCI_ACPI=y
-CONFIG_HOTPLUG_PCI_CPCI=y
-CONFIG_IA32_EMULATION=y
-CONFIG_IA32_AOUT=y
-CONFIG_X86_X32=y
-CONFIG_NET=y
-CONFIG_PACKET=y
-CONFIG_UNIX=y
-CONFIG_XFRM_SUB_POLICY=y
-CONFIG_XFRM_MIGRATE=y
-CONFIG_INET=y
-CONFIG_IP_MULTICAST=y
-CONFIG_IP_ADVANCED_ROUTER=y
-CONFIG_IP_FIB_TRIE_STATS=y
-CONFIG_IP_MULTIPLE_TABLES=y
-CONFIG_IP_ROUTE_MULTIPATH=y
-CONFIG_IP_ROUTE_VERBOSE=y
-CONFIG_IP_MROUTE=y
-CONFIG_IP_MROUTE_MULTIPLE_TABLES=y
-CONFIG_IP_PIMSM_V1=y
-CONFIG_IP_PIMSM_V2=y
-CONFIG_SYN_COOKIES=y
-# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_INET_DIAG is not set
-CONFIG_TCP_CONG_ADVANCED=y
-# CONFIG_TCP_CONG_BIC is not set
-# CONFIG_TCP_CONG_WESTWOOD is not set
-# CONFIG_TCP_CONG_HTCP is not set
-CONFIG_TCP_MD5SIG=y
-CONFIG_IPV6_ROUTER_PREF=y
-CONFIG_IPV6_ROUTE_INFO=y
-CONFIG_IPV6_OPTIMISTIC_DAD=y
-CONFIG_IPV6_MIP6=y
-# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET6_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET6_XFRM_MODE_BEET is not set
-# CONFIG_IPV6_SIT is not set
-CONFIG_IPV6_MULTIPLE_TABLES=y
-CONFIG_IPV6_SUBTREES=y
-CONFIG_IPV6_MROUTE=y
-CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
-CONFIG_IPV6_PIMSM_V2=y
-CONFIG_NETFILTER=y
-CONFIG_IP_NF_IPTABLES=m
-CONFIG_NET_SCHED=y
-CONFIG_NET_EMATCH=y
-CONFIG_NET_CLS_ACT=y
-CONFIG_DCB=y
-CONFIG_MPLS=y
-CONFIG_NET_MPLS_GSO=y
-CONFIG_NET_L3_MASTER_DEV=y
-CONFIG_CGROUP_NET_PRIO=y
-CONFIG_CGROUP_NET_CLASSID=y
-CONFIG_BPF_JIT=y
-CONFIG_LWTUNNEL=y
-# CONFIG_UEVENT_HELPER is not set
-CONFIG_DEVTMPFS=y
-# CONFIG_FIRMWARE_IN_KERNEL is not set
-CONFIG_CONNECTOR=y
-# CONFIG_PNP_DEBUG_MESSAGES is not set
-CONFIG_VIRTIO_BLK=y
-# CONFIG_SCSI_PROC_FS is not set
-CONFIG_BLK_DEV_SD=m
-CONFIG_CHR_DEV_SG=m
-CONFIG_SCSI_CONSTANTS=y
-CONFIG_SCSI_LOGGING=y
-CONFIG_SCSI_SCAN_ASYNC=y
-CONFIG_MEGARAID_NEWGEN=y
-CONFIG_SCSI_DH=y
-CONFIG_ATA=y
-# CONFIG_SATA_PMP is not set
-CONFIG_SATA_AHCI=y
-# CONFIG_ATA_SFF is not set
-CONFIG_MD=y
-CONFIG_NETDEVICES=y
-CONFIG_NET_FC=y
-CONFIG_VIRTIO_NET=y
-# CONFIG_NET_VENDOR_ARC is not set
-CONFIG_NET_TULIP=y
-# CONFIG_NET_VENDOR_SEEQ is not set
-CONFIG_INPUT_EVDEV=m
-CONFIG_MOUSE_PS2=m
-CONFIG_MOUSE_PS2_ELANTECH=y
-CONFIG_MOUSE_PS2_SENTELIC=y
-CONFIG_MOUSE_PS2_VMMOUSE=y
-CONFIG_INPUT_JOYSTICK=y
-CONFIG_INPUT_TABLET=y
-CONFIG_INPUT_TOUCHSCREEN=y
-CONFIG_INPUT_MISC=y
-CONFIG_INPUT_PCSPKR=m
-# CONFIG_SERIO_SERPORT is not set
-CONFIG_SERIO_RAW=m
-CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
-# CONFIG_LEGACY_PTYS is not set
-CONFIG_SERIAL_NONSTANDARD=y
-# CONFIG_DEVKMEM is not set
-CONFIG_SERIAL_8250=y
-# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set
-CONFIG_SERIAL_8250_CONSOLE=y
-CONFIG_SERIAL_8250_NR_UARTS=32
-CONFIG_SERIAL_8250_EXTENDED=y
-CONFIG_SERIAL_8250_MANY_PORTS=y
-CONFIG_SERIAL_8250_SHARE_IRQ=y
-CONFIG_SERIAL_8250_RSA=y
-# CONFIG_HW_RANDOM is not set
-CONFIG_HPET=y
-CONFIG_I2C=y
-CONFIG_I2C_I801=m
-CONFIG_SPI=y
-CONFIG_PINCTRL_BAYTRAIL=y
-CONFIG_PINCTRL_CHERRYVIEW=y
-CONFIG_PINCTRL_BROXTON=y
-CONFIG_PINCTRL_SUNRISEPOINT=y
-CONFIG_GPIO_SYSFS=y
-CONFIG_GPIO_INTEL_MID=y
-CONFIG_POWER_SUPPLY=y
-CONFIG_THERMAL_WRITABLE_TRIPS=y
-CONFIG_THERMAL_GOV_FAIR_SHARE=y
-CONFIG_THERMAL_GOV_BANG_BANG=y
-CONFIG_THERMAL_GOV_USER_SPACE=y
-# CONFIG_X86_PKG_TEMP_THERMAL is not set
-CONFIG_WATCHDOG=y
-CONFIG_ITCO_WDT=m
-CONFIG_ITCO_VENDOR_SUPPORT=y
-CONFIG_LPC_ICH=m
-CONFIG_AGP=y
-CONFIG_AGP_AMD64=y
-CONFIG_AGP_INTEL=y
-CONFIG_AGP_SIS=y
-CONFIG_AGP_VIA=y
-CONFIG_VGA_SWITCHEROO=y
-CONFIG_FB=y
-CONFIG_FIRMWARE_EDID=y
-CONFIG_FB_MODE_HELPERS=y
-CONFIG_FB_TILEBLITTING=y
-CONFIG_FB_VESA=y
-CONFIG_FB_EFI=y
-CONFIG_BACKLIGHT_LCD_SUPPORT=y
-# CONFIG_LCD_CLASS_DEVICE is not set
-CONFIG_BACKLIGHT_CLASS_DEVICE=y
-# CONFIG_BACKLIGHT_GENERIC is not set
-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
-CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
-# CONFIG_HID is not set
-CONFIG_NEW_LEDS=y
-CONFIG_LEDS_CLASS=y
-CONFIG_LEDS_TRIGGERS=y
-CONFIG_LEDS_TRIGGER_CPU=y
-CONFIG_ACCESSIBILITY=y
-CONFIG_A11Y_BRAILLE_CONSOLE=y
-CONFIG_EDAC=y
-# CONFIG_EDAC_DECODE_MCE is not set
-CONFIG_RTC_CLASS=y
-CONFIG_DMADEVICES=y
-CONFIG_VIRT_DRIVERS=y
-CONFIG_VIRTIO_PCI=y
-CONFIG_AMD_IOMMU=y
-CONFIG_AMD_IOMMU_V2=y
-CONFIG_INTEL_IOMMU=y
-CONFIG_INTEL_IOMMU_SVM=y
-# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
-CONFIG_IRQ_REMAP=y
-CONFIG_PM_DEVFREQ=y
-CONFIG_MEMORY=y
-CONFIG_GENERIC_PHY=y
-CONFIG_POWERCAP=y
-CONFIG_DMI_SYSFS=y
-CONFIG_ISCSI_IBFT_FIND=y
-CONFIG_EXT4_FS=m
-CONFIG_EXT4_FS_POSIX_ACL=y
-CONFIG_EXT4_FS_SECURITY=y
-CONFIG_FS_DAX=y
-CONFIG_FANOTIFY=y
-CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
-CONFIG_QUOTA=y
-CONFIG_QUOTA_NETLINK_INTERFACE=y
-CONFIG_AUTOFS4_FS=m
-CONFIG_PROC_KCORE=y
-CONFIG_TMPFS=y
-CONFIG_TMPFS_POSIX_ACL=y
-CONFIG_HUGETLBFS=y
-# CONFIG_EFIVAR_FS is not set
-CONFIG_NLS_DEFAULT="utf8"
-CONFIG_PRINTK_TIME=y
-CONFIG_BOOT_PRINTK_DELAY=y
-CONFIG_DYNAMIC_DEBUG=y
-CONFIG_STRIP_ASM_SYMS=y
-# CONFIG_UNUSED_SYMBOLS is not set
-# CONFIG_FRAME_POINTER is not set
-CONFIG_MAGIC_SYSRQ=y
-CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6
-CONFIG_PAGE_POISONING=y
-CONFIG_DEBUG_MEMORY_INIT=y
-CONFIG_LOCKUP_DETECTOR=y
-CONFIG_SCHEDSTATS=y
-CONFIG_SCHED_STACK_END_CHECK=y
-CONFIG_FTRACE_SYSCALLS=y
-CONFIG_TRACER_SNAPSHOT=y
-CONFIG_STACK_TRACER=y
-CONFIG_BLK_DEV_IO_TRACE=y
-CONFIG_UPROBE_EVENT=y
-CONFIG_MMIOTRACE=y
-CONFIG_MEMTEST=y
-CONFIG_STRICT_DEVMEM=y
-# CONFIG_X86_VERBOSE_BOOTUP is not set
-CONFIG_EARLY_PRINTK_EFI=y
-# CONFIG_DEBUG_RODATA_TEST is not set
-CONFIG_DEBUG_SET_MODULE_RONX=y
-CONFIG_OPTIMIZE_INLINING=y
-CONFIG_KEYS=y
-CONFIG_SECURITY_DMESG_RESTRICT=y
-CONFIG_SECURITY=y
-CONFIG_SECURITY_NETWORK_XFRM=y
-CONFIG_SECURITY_SELINUX=y
-CONFIG_SECURITY_TOMOYO=y
-CONFIG_SECURITY_APPARMOR=y
-CONFIG_SECURITY_YAMA=y
-CONFIG_IMA=y
-CONFIG_IMA_DEFAULT_HASH_SHA256=y
-CONFIG_IMA_APPRAISE=y
-CONFIG_DEFAULT_SECURITY_DAC=y
-# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
-# CONFIG_CRYPTO_ECHAINIV is not set
-CONFIG_CRYPTO_CRC32C=y
-CONFIG_CRYPTO_CRC32C_INTEL=y
-CONFIG_CRYPTO_SHA256=y
-CONFIG_CRYPTO_DEV_CCP=y
-# CONFIG_CRYPTO_DEV_CCP_DD is not set
-# CONFIG_VIRTUALIZATION is not set
-# CONFIG_XZ_DEC_POWERPC is not set
-# CONFIG_XZ_DEC_IA64 is not set
-# CONFIG_XZ_DEC_ARM is not set
-# CONFIG_XZ_DEC_ARMTHUMB is not set
-# CONFIG_XZ_DEC_SPARC is not set
diff --git a/recipes-kernel/linux/linux-cip-common.inc b/recipes-kernel/linux/linux-cip-common.inc
index 8bd0f99..d45a3b0 100644
--- a/recipes-kernel/linux/linux-cip-common.inc
+++ b/recipes-kernel/linux/linux-cip-common.inc
@@ -26,4 +26,4 @@ SRC_URI += " \
SRC_URI_append = " ${@conditional("USE_CIP_KERNEL_CONFIG", "1", \
"git://gitlab.com/cip-project/cip-kernel/cip-kernel-config.git;protocol=https;destsuffix=cip-kernel-config;name=cip-kernel-config", \
"file://${KERNEL_DEFCONFIG}",d)}"
-SRCREV_cip-kernel-config ?= "f88ee1e75253104f975263cf4d0bddd557388197"
+SRCREV_cip-kernel-config ?= "db2085219b5f28ed7c3e0fbdf93b7867947958a8"
Thanks, applied to next.

Jan

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


Re: [isar-cip-core 1/2] opt: Add kas option file for security image

Venkata Pyla
 

On Thu, Jul 30, 2020 at 02:51 PM, Jan Kiszka wrote:


On 30.07.20 11:10, venkata.pyla@toshiba-tsip.com wrote:
From: venkata pyla <venkata.pyla@toshiba-tsip.com>

Signed-off-by: Venkata Pyla <venkata.pyla@toshiba-tsip.com>
Different capitalization of your name. Only reporting that as my tooling
detected this mismatch. It checks if signed-off and authorship match.
I will correct this problem thank you.


Both patches applied to next - let's get CI started.
Thank you for applying the patches.


Thanks,
Jan

---
README.md | 2 +-
kas/opt/security.yml | 14 ++++++++++++++
2 files changed, 15 insertions(+), 1 deletion(-)
create mode 100644 kas/opt/security.yml

diff --git a/README.md b/README.md
index 26fbbef..250dbad 100644
--- a/README.md
+++ b/README.md
@@ -39,7 +39,7 @@ card, run
## Building Security target images
Building images for QEMU x86-64bit machine

- ./kas-docker --isar build --target cip-core-image-security
kas.yml:board-qemu-amd64.yml
+ ./kas-docker --isar build
kas-cip.yml:kas/board/qemu-amd64.yml:kas/opt/security.yml

Run the generated securiy images on QEMU (x86-64bit)

diff --git a/kas/opt/security.yml b/kas/opt/security.yml
new file mode 100644
index 0000000..237cbeb
--- /dev/null
+++ b/kas/opt/security.yml
@@ -0,0 +1,14 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Toshiba Corporation, 2020
+#
+# Authors:
+# Venkata Pyla <venkata.pyla@toshiba-tsip.com>
+#
+# SPDX-License-Identifier: MIT
+#
+header:
+ version: 8
+
+target: cip-core-image-security
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


Re: [isar-cip-core 1/2] opt: Add kas option file for security image

Jan Kiszka
 

On 30.07.20 11:10, venkata.pyla@toshiba-tsip.com wrote:
From: venkata pyla <venkata.pyla@toshiba-tsip.com>
Signed-off-by: Venkata Pyla <venkata.pyla@toshiba-tsip.com>
Different capitalization of your name. Only reporting that as my tooling detected this mismatch. It checks if signed-off and authorship match.

Both patches applied to next - let's get CI started.

Thanks,
Jan

---
README.md | 2 +-
kas/opt/security.yml | 14 ++++++++++++++
2 files changed, 15 insertions(+), 1 deletion(-)
create mode 100644 kas/opt/security.yml
diff --git a/README.md b/README.md
index 26fbbef..250dbad 100644
--- a/README.md
+++ b/README.md
@@ -39,7 +39,7 @@ card, run
## Building Security target images
Building images for QEMU x86-64bit machine
- ./kas-docker --isar build --target cip-core-image-security kas.yml:board-qemu-amd64.yml
+ ./kas-docker --isar build kas-cip.yml:kas/board/qemu-amd64.yml:kas/opt/security.yml
Run the generated securiy images on QEMU (x86-64bit)
diff --git a/kas/opt/security.yml b/kas/opt/security.yml
new file mode 100644
index 0000000..237cbeb
--- /dev/null
+++ b/kas/opt/security.yml
@@ -0,0 +1,14 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Toshiba Corporation, 2020
+#
+# Authors:
+# Venkata Pyla <venkata.pyla@toshiba-tsip.com>
+#
+# SPDX-License-Identifier: MIT
+#
+header:
+ version: 8
+
+target: cip-core-image-security
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux


Re: CIP Patchwork

Nobuhiro Iwamatsu
 

Hi,

-----Original Message-----
From: Chris Paterson [mailto:Chris.Paterson2@renesas.com]
Sent: Thursday, July 23, 2020 6:37 PM
To: masashi.kudo@cybertrust.co.jp; iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT)
<nobuhiro1.iwamatsu@toshiba.co.jp>; pavel@denx.de; ben.hutchings@codethink.co.uk; SZ.Lin@moxa.com; wens@csie.org
Cc: cip-dev@lists.cip-project.org
Subject: CIP Patchwork

Hello all,

CIP has a Patchwork instance [0] that monitors the cip-dev mainline list for patches.

It doesn't look like it's particularly maintained, with most patches in the "new" state.
As a project, do we want to start maintaining Patchwork? Should we kill it off? Or just stick with the status-quo?

We briefly discussed this in the IRC meeting today, but I thought we should check with a wider audience before making
a decision.
Not all, I sometime checked and updated this.
There are more non-kernel patches, so I re-check this.
And I use this for patch tracking and patch appling.



So, any thoughts?

[0] https://patchwork.kernel.org/project/cip-dev/list/

Kind regards, Chris
Best regards,
Nobuhiro


[isar-cip-core 1/2] opt: Add kas option file for security image

Venkata Pyla
 

From: venkata pyla <venkata.pyla@toshiba-tsip.com>

Signed-off-by: Venkata Pyla <venkata.pyla@toshiba-tsip.com>
---
README.md | 2 +-
kas/opt/security.yml | 14 ++++++++++++++
2 files changed, 15 insertions(+), 1 deletion(-)
create mode 100644 kas/opt/security.yml

diff --git a/README.md b/README.md
index 26fbbef..250dbad 100644
--- a/README.md
+++ b/README.md
@@ -39,7 +39,7 @@ card, run
## Building Security target images
Building images for QEMU x86-64bit machine

- ./kas-docker --isar build --target cip-core-image-security kas.yml:board-qemu-amd64.yml
+ ./kas-docker --isar build kas-cip.yml:kas/board/qemu-amd64.yml:kas/opt/security.yml

Run the generated securiy images on QEMU (x86-64bit)

diff --git a/kas/opt/security.yml b/kas/opt/security.yml
new file mode 100644
index 0000000..237cbeb
--- /dev/null
+++ b/kas/opt/security.yml
@@ -0,0 +1,14 @@
+#
+# CIP Core, generic profile
+#
+# Copyright (c) Toshiba Corporation, 2020
+#
+# Authors:
+# Venkata Pyla <venkata.pyla@toshiba-tsip.com>
+#
+# SPDX-License-Identifier: MIT
+#
+header:
+ version: 8
+
+target: cip-core-image-security
--
2.20.1

The information contained in this e-mail message and in any
attachments/annexure/appendices is confidential to the
recipient and may contain privileged information.
If you are not the intended recipient, please notify the
sender and delete the message along with any
attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the
message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender
specifically states them to be the views of
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.

Although this transmission and any attachments are believed to be
free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility
of the recipient to ensure that it is virus free and no responsibility
is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or
damage arising in any way from its use.


[isar-cip-core 0/2] add security image to ci

Venkata Pyla
 

From: venkata pyla <venkata.pyla@toshiba-tsip.com>

Add kas option file for security image
Add security image to ci

venkata pyla (2):
opt: Add kas option file for security image
ci: Add security image

.gitlab-ci.yml | 3 +++
README.md | 2 +-
kas/opt/security.yml | 14 ++++++++++++++
3 files changed, 18 insertions(+), 1 deletion(-)
create mode 100644 kas/opt/security.yml

--
2.20.1

The information contained in this e-mail message and in any
attachments/annexure/appendices is confidential to the
recipient and may contain privileged information.
If you are not the intended recipient, please notify the
sender and delete the message along with any
attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the
message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender
specifically states them to be the views of
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.

Although this transmission and any attachments are believed to be
free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility
of the recipient to ensure that it is virus free and no responsibility
is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or
damage arising in any way from its use.


[isar-cip-core 2/2] ci: Add security image

Venkata Pyla
 

From: venkata pyla <venkata.pyla@toshiba-tsip.com>

Signed-off-by: Venkata Pyla <venkata.pyla@toshiba-tsip.com>
---
.gitlab-ci.yml | 3 +++
1 file changed, 3 insertions(+)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 241b09e..3fe7af2 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -27,3 +27,6 @@ all:
- sudo rm -rf build/tmp
- kas build kas-cip.yml:kas/board/rzg2m.yml:kas/opt/rt.yml:kas/opt/targz-img.yml
- scripts/deploy-cip-core.sh buster hihope-rzg2m renesas/r8a774a1-hihope-rzg2m-ex.dtb
+
+ - sudo rm -rf build/tmp
+ - kas build kas-cip.yml:kas/board/qemu-amd64.yml:kas/opt/security.yml
--
2.20.1

The information contained in this e-mail message and in any
attachments/annexure/appendices is confidential to the
recipient and may contain privileged information.
If you are not the intended recipient, please notify the
sender and delete the message along with any
attachments/annexure/appendices. You should not disclose,
copy or otherwise use the information contained in the
message or any annexure. Any views expressed in this e-mail
are those of the individual sender except where the sender
specifically states them to be the views of
Toshiba Software India Pvt. Ltd. (TSIP),Bangalore.

Although this transmission and any attachments are believed to be
free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility
of the recipient to ensure that it is virus free and no responsibility
is accepted by Toshiba Embedded Software India Pvt. Ltd, for any loss or
damage arising in any way from its use.


Re: CIP IRC weekly meeting today

Akihiro Suzuki
 

Hi Kudo-san,

I'm sorry I won't be able to join the IRC meeting today.
SW Updates WG still work on supporting HTTPS connection between SWUpdate and hawkBit.
https://gitlab.com/cip-project/cip-sw-updates/cip-sw-updates-tasks/-/issues/8

Thanks,
Suzuki

-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of masashi.kudo@cybertrust.co.jp
Sent: Thursday, July 30, 2020 10:57 AM
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] CIP IRC weekly meeting today

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting from the first week of Apr. according to TSC meeting*
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=7&day=30&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

USWest USEast UK DE TW JP
02:00 05:00 10:00 11:00 17:00 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last meeting minutes:
https://lore.kernel.org/cip-dev/OSAPR01MB23857705B82D0D163B5E5211B7770@OSAPR01MB2385.jpnprd01.prod.outlook.com/T/#m873e67bf005078f86fe9f659682614def4a448a6

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - iwamatsu
2. Post LTP results to KernelCI - patersonc
3. Email Kernel team/cip-dev about patchwork usage - patersonc
Old AI "Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu" was taken care by SZ-san and was closed last week.

* Kernel maintenance updates
* Kernel testing
* Software update
* CIP Security
* AOB

The meeting will take 30 min, although it can be extended to an hour if it makes sense and those involved in the topics can stay. Otherwise, the topic will be taken offline or in the next meeting.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.


Remove QEMU kernel config from isar-cip-core

Daniel Sangorrin <daniel.sangorrin@...>
 

Hi,

The following patch removes QEMU's config from isar-cip-core and uses cip-kernel-config's instead.
[isar-cip-core] qemu-amd64: use cip-kernel-config file

As I say in the commit message, I had to upgrade cip-kernel-config's commit id which could have effects on other targets. I boot-tested QEMU but I hope the CI will test for regressions in other targets as well.

If you prefer, I could override the cip-kernel-config commit id on the QEMU machine's configuration file only to avoid regressions at all.

For your reference, I put below a diff between the isar-cip-core configuration and the cip-kernel-config configuration.
I can put it in the commit message if you prefer, but I thought it was too long.
There are a lot of changes and I have not really reviewed them so we may need to do that and postpone this patch.
For example, -CONFIG_CC_STACKPROTECTOR_STRONG=y doesn't look like a good change.

On the other hand, I wish that cip-kernel-config had the base kernel config (per-arch) separated from the target-dependent options.
For example, CONFIG_CC_STACKPROTECTOR_STRONG=y could be part of the base.

Another thing that needs to be fixed is the configuration for the RT kernel.
ATM, we are appending a set of config fragments (preempt-rt.cfg i think) in isar-cip-core. However, cip-kernel-config has its own folder for linux-rt configs.

Thanks,
Daniel

List of changes from isar-cip-core's config to cip-kernel-config's config.

--- isar-sorted 2020-07-30 11:05:43.418894507 +0900
+++ cip-sorted 2020-07-30 11:06:21.358244870 +0900
@@ -1,318 +1,250 @@
-# CONFIG_ACPI_AC is not set
-# CONFIG_ACPI_BATTERY is not set
-# CONFIG_ACPI_FAN is not set
-# CONFIG_ACPI_THERMAL is not set
-# CONFIG_ATA_SFF is not set
-# CONFIG_BACKLIGHT_GENERIC is not set
# CONFIG_COMPAT_BRK is not set
-# CONFIG_CRYPTO_DEV_CCP_DD is not set
-# CONFIG_CRYPTO_ECHAINIV is not set
-# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
-# CONFIG_DEBUG_RODATA_TEST is not set
-# CONFIG_DEVKMEM is not set
-# CONFIG_EDAC_DECODE_MCE is not set
-# CONFIG_EFIVAR_FS is not set
-# CONFIG_FIRMWARE_IN_KERNEL is not set
-# CONFIG_FRAME_POINTER is not set
-# CONFIG_HID is not set
-# CONFIG_HW_RANDOM is not set
-# CONFIG_INET6_XFRM_MODE_BEET is not set
-# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET6_XFRM_MODE_TUNNEL is not set
+# CONFIG_HPET_MMAP is not set
+# CONFIG_HW_RANDOM_AMD is not set
+# CONFIG_HW_RANDOM_INTEL is not set
# CONFIG_INET_DIAG is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
-# CONFIG_IPV6_SIT is not set
# CONFIG_LCD_CLASS_DEVICE is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_LOCALVERSION_AUTO is not set
-# CONFIG_MEMCG_SWAP_ENABLED is not set
-# CONFIG_NET_VENDOR_ARC is not set
-# CONFIG_NET_VENDOR_SEEQ is not set
-# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
-# CONFIG_PNP_DEBUG_MESSAGES is not set
-# CONFIG_SATA_PMP is not set
-# CONFIG_SCSI_PROC_FS is not set
-# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set
-# CONFIG_SERIO_SERPORT is not set
+# CONFIG_LOGO_LINUX_MONO is not set
+# CONFIG_LOGO_LINUX_VGA16 is not set
+# CONFIG_MTRR_SANITIZER is not set
+# CONFIG_NETFILTER_ADVANCED is not set
+# CONFIG_PRINT_QUOTA_WARNING is not set
+# CONFIG_RTC_HCTOSYS is not set
+# CONFIG_SCHED_DEBUG is not set
+# CONFIG_SCSI_LOWLEVEL is not set
# CONFIG_TCP_CONG_BIC is not set
# CONFIG_TCP_CONG_HTCP is not set
# CONFIG_TCP_CONG_WESTWOOD is not set
-# CONFIG_UEVENT_HELPER is not set
# CONFIG_UNUSED_SYMBOLS is not set
-# CONFIG_VIRTUALIZATION is not set
-# CONFIG_X86_EXTENDED_PLATFORM is not set
-# CONFIG_X86_PKG_TEMP_THERMAL is not set
-# CONFIG_X86_VERBOSE_BOOTUP is not set
-# CONFIG_XZ_DEC_ARM is not set
-# CONFIG_XZ_DEC_ARMTHUMB is not set
-# CONFIG_XZ_DEC_IA64 is not set
-# CONFIG_XZ_DEC_POWERPC is not set
-# CONFIG_XZ_DEC_SPARC is not set
-CONFIG_A11Y_BRAILLE_CONSOLE=y
-CONFIG_ACCESSIBILITY=y
-CONFIG_ACPI_APEI=y
-CONFIG_ACPI_APEI_GHES=y
-CONFIG_ACPI_APEI_MEMORY_FAILURE=y
-CONFIG_ACPI_APEI_PCIEAER=y
-CONFIG_ACPI_BGRT=y
-CONFIG_ACPI_BUTTON=m
+CONFIG_8139TOO=y
CONFIG_ACPI_DOCK=y
-CONFIG_ACPI_EXTLOG=y
-CONFIG_ACPI_HOTPLUG_MEMORY=y
-CONFIG_ACPI_PCI_SLOT=y
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
CONFIG_AGP_INTEL=y
-CONFIG_AGP_SIS=y
-CONFIG_AGP_VIA=y
CONFIG_AMD_IOMMU=y
-CONFIG_AMD_IOMMU_V2=y
+CONFIG_AMIGA_PARTITION=y
CONFIG_ATA=y
-CONFIG_AUTOFS4_FS=m
-CONFIG_BACKLIGHT_CLASS_DEVICE=y
-CONFIG_BACKLIGHT_LCD_SUPPORT=y
-CONFIG_BLK_CGROUP=y
-CONFIG_BLK_DEV_BSGLIB=y
+CONFIG_ATA_PIIX=y
+CONFIG_AUDIT=y
+CONFIG_AUTOFS4_FS=y
+CONFIG_BINFMT_MISC=y
+CONFIG_BLK_DEV_DM=y
CONFIG_BLK_DEV_INITRD=y
-CONFIG_BLK_DEV_INTEGRITY=y
CONFIG_BLK_DEV_IO_TRACE=y
-CONFIG_BLK_DEV_SD=m
-CONFIG_BLK_DEV_THROTTLING=y
-CONFIG_BOOT_PRINTK_DELAY=y
-CONFIG_BPF_JIT=y
-CONFIG_BPF_SYSCALL=y
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_DEV_MD=y
+CONFIG_BLK_DEV_SD=y
+CONFIG_BLK_DEV_SR=y
+CONFIG_BLK_DEV_SR_VENDOR=y
+CONFIG_BSD_DISKLABEL=y
CONFIG_BSD_PROCESS_ACCT=y
-CONFIG_BSD_PROCESS_ACCT_V3=y
CONFIG_CALGARY_IOMMU=y
-CONFIG_CC_STACKPROTECTOR_STRONG=y
-CONFIG_CFQ_GROUP_IOSCHED=y
-CONFIG_CFS_BANDWIDTH=y
+CONFIG_CFG80211=y
+CONFIG_CGROUPS=y
CONFIG_CGROUP_CPUACCT=y
-CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_FREEZER=y
-CONFIG_CGROUP_NET_CLASSID=y
-CONFIG_CGROUP_NET_PRIO=y
-CONFIG_CGROUP_PERF=y
-CONFIG_CGROUP_PIDS=y
-CONFIG_CHECKPOINT_RESTORE=y
-CONFIG_CHR_DEV_SG=m
+CONFIG_CGROUP_SCHED=y
+CONFIG_CHR_DEV_SG=y
CONFIG_CONNECTOR=y
CONFIG_CPUSETS=y
-CONFIG_CPU_FREQ=y
-CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE=y
+CONFIG_CPU_FREQ_GOV_ONDEMAND=y
+CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CRASH_DUMP=y
-CONFIG_CRYPTO_CRC32C=y
-CONFIG_CRYPTO_CRC32C_INTEL=y
-CONFIG_CRYPTO_DEV_CCP=y
-CONFIG_CRYPTO_SHA256=y
-CONFIG_DCB=y
-CONFIG_DEBUG_MEMORY_INIT=y
-CONFIG_DEBUG_SET_MODULE_RONX=y
-CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
-CONFIG_DEFAULT_SECURITY_DAC=y
-CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
+CONFIG_DEBUG_BOOT_PARAMS=y
+CONFIG_DEBUG_DEVRES=y
+CONFIG_DEBUG_KERNEL=y
+CONFIG_DEBUG_STACKOVERFLOW=y
+CONFIG_DEBUG_STACK_USAGE=y
CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
CONFIG_DMADEVICES=y
-CONFIG_DMI_SYSFS=y
-CONFIG_DYNAMIC_DEBUG=y
-CONFIG_EARLY_PRINTK_EFI=y
+CONFIG_DM_MIRROR=y
+CONFIG_DM_ZERO=y
+CONFIG_DRM=y
+CONFIG_DRM_I915=y
+CONFIG_E1000=y
+CONFIG_E1000E=y
+CONFIG_E100=y
+CONFIG_EARLY_PRINTK_DBGP=y
CONFIG_EDAC=y
+CONFIG_EEEPC_LAPTOP=y
CONFIG_EFI=y
-CONFIG_EFI_MIXED=y
-CONFIG_EFI_STUB=y
-CONFIG_EXPERT=y
-CONFIG_EXT4_FS=m
+CONFIG_EFI_VARS=y
+CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
-CONFIG_FANOTIFY=y
-CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
-CONFIG_FB=y
CONFIG_FB_EFI=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
-CONFIG_FB_VESA=y
-CONFIG_FHANDLE=y
-CONFIG_FIRMWARE_EDID=y
-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
-CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
-CONFIG_FRONTSWAP=y
-CONFIG_FS_DAX=y
-CONFIG_FTRACE_SYSCALLS=y
-CONFIG_GART_IOMMU=y
-CONFIG_GENERIC_PHY=y
-CONFIG_GPIO_INTEL_MID=y
-CONFIG_GPIO_SYSFS=y
+CONFIG_FDDI=y
+CONFIG_FORCEDETH=y
+CONFIG_HAMRADIO=y
CONFIG_HIBERNATION=y
+CONFIG_HIDRAW=y
+CONFIG_HID_GYRATION=y
+CONFIG_HID_NTRIG=y
+CONFIG_HID_PANTHERLORD=y
+CONFIG_HID_PETALYNX=y
+CONFIG_HID_PID=y
+CONFIG_HID_SAMSUNG=y
+CONFIG_HID_SONY=y
+CONFIG_HID_SUNPLUS=y
+CONFIG_HID_TOPSEED=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_HOTPLUG_PCI=y
-CONFIG_HOTPLUG_PCI_ACPI=y
-CONFIG_HOTPLUG_PCI_CPCI=y
-CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_HPET=y
CONFIG_HUGETLBFS=y
-CONFIG_HYPERVISOR_GUEST=y
-CONFIG_I2C=y
-CONFIG_I2C_I801=m
-CONFIG_IA32_AOUT=y
+CONFIG_HW_RANDOM=y
+CONFIG_HZ_1000=y
+CONFIG_I2C_I801=y
CONFIG_IA32_EMULATION=y
-CONFIG_IKCONFIG=m
-CONFIG_IMA=y
-CONFIG_IMA_APPRAISE=y
-CONFIG_IMA_DEFAULT_HASH_SHA256=y
+CONFIG_INET6_AH=y
+CONFIG_INET6_ESP=y
CONFIG_INET=y
-CONFIG_INPUT_EVDEV=m
+CONFIG_INPUT_EVDEV=y
CONFIG_INPUT_JOYSTICK=y
CONFIG_INPUT_MISC=y
-CONFIG_INPUT_PCSPKR=m
+CONFIG_INPUT_POLLDEV=y
CONFIG_INPUT_TABLET=y
CONFIG_INPUT_TOUCHSCREEN=y
-CONFIG_INTEL_IDLE=y
CONFIG_INTEL_IOMMU=y
-CONFIG_INTEL_IOMMU_SVM=y
-CONFIG_IOSF_MBI=y
-CONFIG_IPV6_MIP6=y
-CONFIG_IPV6_MROUTE=y
-CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
-CONFIG_IPV6_MULTIPLE_TABLES=y
-CONFIG_IPV6_OPTIMISTIC_DAD=y
-CONFIG_IPV6_PIMSM_V2=y
-CONFIG_IPV6_ROUTER_PREF=y
-CONFIG_IPV6_ROUTE_INFO=y
-CONFIG_IPV6_SUBTREES=y
+CONFIG_IP6_NF_FILTER=y
+CONFIG_IP6_NF_IPTABLES=y
+CONFIG_IP6_NF_MANGLE=y
+CONFIG_IP6_NF_MATCH_IPV6HEADER=y
+CONFIG_IP6_NF_TARGET_REJECT=y
CONFIG_IP_ADVANCED_ROUTER=y
-CONFIG_IP_FIB_TRIE_STATS=y
CONFIG_IP_MROUTE=y
-CONFIG_IP_MROUTE_MULTIPLE_TABLES=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_MULTIPLE_TABLES=y
-CONFIG_IP_NF_IPTABLES=m
+CONFIG_IP_NF_FILTER=y
+CONFIG_IP_NF_IPTABLES=y
+CONFIG_IP_NF_MANGLE=y
+CONFIG_IP_NF_TARGET_REJECT=y
CONFIG_IP_PIMSM_V1=y
CONFIG_IP_PIMSM_V2=y
+CONFIG_IP_PNP=y
+CONFIG_IP_PNP_BOOTP=y
+CONFIG_IP_PNP_DHCP=y
+CONFIG_IP_PNP_RARP=y
CONFIG_IP_ROUTE_MULTIPATH=y
CONFIG_IP_ROUTE_VERBOSE=y
-CONFIG_IRQ_REMAP=y
-CONFIG_ISCSI_IBFT_FIND=y
-CONFIG_ITCO_VENDOR_SUPPORT=y
-CONFIG_ITCO_WDT=m
+CONFIG_ISO9660_FS=y
+CONFIG_JOLIET=y
CONFIG_JUMP_LABEL=y
-CONFIG_KALLSYMS_ALL=y
+CONFIG_KARMA_PARTITION=y
CONFIG_KEXEC=y
-CONFIG_KEXEC_FILE=y
-CONFIG_KEXEC_VERIFY_SIG=y
-CONFIG_KEYS=y
CONFIG_KPROBES=y
-CONFIG_KSM=y
-CONFIG_LEDS_CLASS=y
-CONFIG_LEDS_TRIGGERS=y
-CONFIG_LEDS_TRIGGER_CPU=y
-CONFIG_LIVEPATCH=y
-CONFIG_LOCKUP_DETECTOR=y
-CONFIG_LPC_ICH=m
-CONFIG_LWTUNNEL=y
+CONFIG_LOGITECH_FF=y
+CONFIG_LOGO=y
+CONFIG_LOG_BUF_SHIFT=18
+CONFIG_MAC80211=y
+CONFIG_MAC80211_LEDS=y
+CONFIG_MACINTOSH_DRIVERS=y
+CONFIG_MAC_EMUMOUSEBTN=y
+CONFIG_MAC_PARTITION=y
CONFIG_MAGIC_SYSRQ=y
-CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6
CONFIG_MD=y
-CONFIG_MEGARAID_NEWGEN=y
-CONFIG_MEMCG=y
-CONFIG_MEMCG_SWAP=y
-CONFIG_MEMORY=y
-CONFIG_MEMORY_FAILURE=y
-CONFIG_MEMORY_HOTPLUG=y
-CONFIG_MEMORY_HOTREMOVE=y
-CONFIG_MEMTEST=y
-CONFIG_MEM_SOFT_DIRTY=y
CONFIG_MICROCODE_AMD=y
-CONFIG_MMIOTRACE=y
+CONFIG_MINIX_SUBPARTITION=y
CONFIG_MODULES=y
+CONFIG_MODULE_FORCE_UNLOAD=y
CONFIG_MODULE_UNLOAD=y
-CONFIG_MODVERSIONS=y
-CONFIG_MOUSE_PS2=m
-CONFIG_MOUSE_PS2_ELANTECH=y
-CONFIG_MOUSE_PS2_SENTELIC=y
-CONFIG_MOUSE_PS2_VMMOUSE=y
-CONFIG_MPLS=y
-CONFIG_NAMESPACES=y
+CONFIG_MSDOS_FS=y
CONFIG_NET=y
+CONFIG_NETCONSOLE=y
CONFIG_NETDEVICES=y
CONFIG_NETFILTER=y
+CONFIG_NETFILTER_XT_MATCH_CONNTRACK=y
+CONFIG_NETFILTER_XT_MATCH_POLICY=y
+CONFIG_NETFILTER_XT_MATCH_STATE=y
+CONFIG_NETFILTER_XT_TARGET_CONNSECMARK=y
+CONFIG_NETFILTER_XT_TARGET_NFLOG=y
+CONFIG_NETFILTER_XT_TARGET_SECMARK=y
+CONFIG_NETFILTER_XT_TARGET_TCPMSS=y
+CONFIG_NETLABEL=y
CONFIG_NET_CLS_ACT=y
CONFIG_NET_EMATCH=y
-CONFIG_NET_FC=y
-CONFIG_NET_L3_MASTER_DEV=y
-CONFIG_NET_MPLS_GSO=y
CONFIG_NET_SCHED=y
CONFIG_NET_TULIP=y
-CONFIG_NEW_LEDS=y
+CONFIG_NFS_FS=y
+CONFIG_NFS_V3_ACL=y
+CONFIG_NFS_V4=y
+CONFIG_NF_CONNTRACK=y
+CONFIG_NF_CONNTRACK_FTP=y
+CONFIG_NF_CONNTRACK_IRC=y
+CONFIG_NF_CONNTRACK_SIP=y
+CONFIG_NF_CT_NETLINK=y
+CONFIG_NLS_ASCII=y
+CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_DEFAULT="utf8"
-CONFIG_NO_HZ_IDLE=y
-CONFIG_NR_CPUS=512
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_UTF8=y
+CONFIG_NO_HZ=y
CONFIG_NUMA=y
-CONFIG_NUMA_BALANCING=y
-CONFIG_NUMA_EMU=y
+CONFIG_NVRAM=y
CONFIG_OPTIMIZE_INLINING=y
+CONFIG_OSF_PARTITION=y
CONFIG_PACKET=y
-CONFIG_PAGE_POISONING=y
-CONFIG_PARAVIRT=y
-CONFIG_PARAVIRT_SPINLOCKS=y
+CONFIG_PANTHERLORD_FF=y
CONFIG_PARTITION_ADVANCED=y
+CONFIG_PATA_AMD=y
+CONFIG_PATA_OLDPIIX=y
+CONFIG_PATA_SCH=y
+CONFIG_PCCARD=y
CONFIG_PCIEPORTBUS=y
-CONFIG_PCI_IOV=y
-CONFIG_PCI_MMCONFIG=y
-CONFIG_PCI_REALLOC_ENABLE_AUTO=y
-CONFIG_PINCTRL_BAYTRAIL=y
-CONFIG_PINCTRL_BROXTON=y
-CONFIG_PINCTRL_CHERRYVIEW=y
-CONFIG_PINCTRL_SUNRISEPOINT=y
-CONFIG_PM_ADVANCED_DEBUG=y
CONFIG_PM_DEBUG=y
-CONFIG_PM_DEVFREQ=y
+CONFIG_PM_TRACE_RTC=y
CONFIG_POSIX_MQUEUE=y
-CONFIG_POWERCAP=y
-CONFIG_POWER_SUPPLY=y
CONFIG_PREEMPT_VOLUNTARY=y
CONFIG_PRINTK_TIME=y
CONFIG_PROC_KCORE=y
CONFIG_PROFILING=y
+CONFIG_PROVIDE_OHCI1394_DMA_INIT=y
+CONFIG_QFMT_V2=y
CONFIG_QUOTA=y
CONFIG_QUOTA_NETLINK_INTERFACE=y
-CONFIG_RANDOMIZE_BASE=y
+CONFIG_R8169=y
+CONFIG_RFKILL=y
+CONFIG_ROOT_NFS=y
CONFIG_RTC_CLASS=y
CONFIG_SATA_AHCI=y
CONFIG_SCHEDSTATS=y
-CONFIG_SCHED_AUTOGROUP=y
-CONFIG_SCHED_SMT=y
-CONFIG_SCHED_STACK_END_CHECK=y
CONFIG_SCSI_CONSTANTS=y
-CONFIG_SCSI_DH=y
-CONFIG_SCSI_LOGGING=y
-CONFIG_SCSI_SCAN_ASYNC=y
+CONFIG_SCSI_SPI_ATTRS=y
CONFIG_SECURITY=y
-CONFIG_SECURITY_APPARMOR=y
-CONFIG_SECURITY_DMESG_RESTRICT=y
-CONFIG_SECURITY_NETWORK_XFRM=y
+CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_SELINUX=y
-CONFIG_SECURITY_TOMOYO=y
-CONFIG_SECURITY_YAMA=y
+CONFIG_SECURITY_SELINUX_BOOTPARAM=y
+CONFIG_SECURITY_SELINUX_DISABLE=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
+CONFIG_SERIAL_8250_DETECT_IRQ=y
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_MANY_PORTS=y
CONFIG_SERIAL_8250_NR_UARTS=32
CONFIG_SERIAL_8250_RSA=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_NONSTANDARD=y
-CONFIG_SERIO_RAW=m
-CONFIG_SFI=y
-CONFIG_SLAB=y
+CONFIG_SGI_PARTITION=y
+CONFIG_SKY2=y
CONFIG_SMP=y
-CONFIG_SPI=y
-CONFIG_STACK_TRACER=y
-CONFIG_STRICT_DEVMEM=y
-CONFIG_STRIP_ASM_SYMS=y
+CONFIG_SND=y
+CONFIG_SND_HDA_HWDEP=y
+CONFIG_SND_HDA_INTEL=y
+CONFIG_SND_HRTIMER=y
+CONFIG_SND_SEQUENCER=y
+CONFIG_SND_SEQ_DUMMY=y
+CONFIG_SOLARIS_X86_PARTITION=y
+CONFIG_SOUND=y
+CONFIG_SUN_PARTITION=y
CONFIG_SYN_COOKIES=y
CONFIG_SYSVIPC=y
CONFIG_TASKSTATS=y
@@ -321,33 +253,32 @@
CONFIG_TASK_XACCT=y
CONFIG_TCP_CONG_ADVANCED=y
CONFIG_TCP_MD5SIG=y
-CONFIG_THERMAL_GOV_BANG_BANG=y
-CONFIG_THERMAL_GOV_FAIR_SHARE=y
-CONFIG_THERMAL_GOV_USER_SPACE=y
-CONFIG_THERMAL_WRITABLE_TRIPS=y
-CONFIG_TMPFS=y
+CONFIG_TIGON3=y
CONFIG_TMPFS_POSIX_ACL=y
-CONFIG_TRACER_SNAPSHOT=y
-CONFIG_TRANSPARENT_HUGEPAGE=y
-CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
+CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_UNIX=y
-CONFIG_UPROBE_EVENT=y
-CONFIG_USERFAULTFD=y
-CONFIG_USER_NS=y
-CONFIG_VGA_SWITCHEROO=y
+CONFIG_UNIXWARE_DISKLABEL=y
+CONFIG_USB=y
+CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
+CONFIG_USB_EHCI_HCD=y
+CONFIG_USB_HIDDEV=y
+CONFIG_USB_MON=y
+CONFIG_USB_OHCI_HCD=y
+CONFIG_USB_PRINTER=y
+CONFIG_USB_STORAGE=y
+CONFIG_USB_UHCI_HCD=y
+CONFIG_VFAT_FS=y
+CONFIG_VGACON_SOFT_SCROLLBACK=y
+CONFIG_VIRTIO_BALLOON=y
CONFIG_VIRTIO_BLK=y
CONFIG_VIRTIO_NET=y
CONFIG_VIRTIO_PCI=y
-CONFIG_VIRT_DRIVERS=y
CONFIG_WATCHDOG=y
-CONFIG_X86_AMD_PLATFORM_DEVICE=y
-CONFIG_X86_INTEL_LPSS=y
-CONFIG_X86_INTEL_MPX=y
-CONFIG_X86_INTEL_PSTATE=y
+CONFIG_X86_ACPI_CPUFREQ=y
+CONFIG_X86_CHECK_BIOS_CORRUPTION=y
+CONFIG_X86_CPUID=y
+CONFIG_X86_MSR=y
CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
-CONFIG_X86_X2APIC=y
-CONFIG_X86_X32=y
-CONFIG_XFRM_MIGRATE=y
-CONFIG_XFRM_SUB_POLICY=y
-CONFIG_ZBUD=y
-CONFIG_ZSWAP=y
+CONFIG_XFRM_USER=y
+CONFIG_YENTA=y
+CONFIG_ZISOFS=y


[isar-cip-core] qemu-amd64: use cip-kernel-config file

Daniel Sangorrin <daniel.sangorrin@...>
 

We should use configs from the cip-kernel-config
repository, which are shared between CIP Core
reference implementations and CIP testing.

I updated the cip-kernel-config commit id because QEMU's
config file was inexistent.

I have built and boot-tested the QEMU target but not
the other ones. Hopefully our CI will detect any
regressions.

Signed-off-by: Daniel Sangorrin <daniel.sangorrin@toshiba.co.jp>
---
conf/machine/qemu-amd64.conf | 2 +
.../linux/files/qemu-amd64_defconfig | 353 ------------------
recipes-kernel/linux/linux-cip-common.inc | 2 +-
3 files changed, 3 insertions(+), 354 deletions(-)
delete mode 100644 recipes-kernel/linux/files/qemu-amd64_defconfig

diff --git a/conf/machine/qemu-amd64.conf b/conf/machine/qemu-amd64.conf
index 7cbd55b..c90d957 100644
--- a/conf/machine/qemu-amd64.conf
+++ b/conf/machine/qemu-amd64.conf
@@ -9,3 +9,5 @@
DISTRO_ARCH = "amd64"

IMAGE_TYPE ?= "ext4-img"
+USE_CIP_KERNEL_CONFIG = "1"
+KERNEL_DEFCONFIG = "cip-kernel-config/4.19.y-cip/x86/cip_qemu_defconfig"
diff --git a/recipes-kernel/linux/files/qemu-amd64_defconfig b/recipes-kernel/linux/files/qemu-amd64_defconfig
deleted file mode 100644
index 7487152..0000000
--- a/recipes-kernel/linux/files/qemu-amd64_defconfig
+++ /dev/null
@@ -1,353 +0,0 @@
-# CONFIG_LOCALVERSION_AUTO is not set
-CONFIG_SYSVIPC=y
-CONFIG_POSIX_MQUEUE=y
-CONFIG_FHANDLE=y
-CONFIG_NO_HZ_IDLE=y
-CONFIG_HIGH_RES_TIMERS=y
-CONFIG_BSD_PROCESS_ACCT=y
-CONFIG_BSD_PROCESS_ACCT_V3=y
-CONFIG_TASKSTATS=y
-CONFIG_TASK_DELAY_ACCT=y
-CONFIG_TASK_XACCT=y
-CONFIG_TASK_IO_ACCOUNTING=y
-CONFIG_IKCONFIG=m
-CONFIG_NUMA_BALANCING=y
-# CONFIG_NUMA_BALANCING_DEFAULT_ENABLED is not set
-CONFIG_CGROUP_FREEZER=y
-CONFIG_CGROUP_PIDS=y
-CONFIG_CGROUP_DEVICE=y
-CONFIG_CPUSETS=y
-CONFIG_CGROUP_CPUACCT=y
-CONFIG_MEMCG=y
-CONFIG_MEMCG_SWAP=y
-# CONFIG_MEMCG_SWAP_ENABLED is not set
-CONFIG_CGROUP_PERF=y
-CONFIG_CFS_BANDWIDTH=y
-CONFIG_BLK_CGROUP=y
-CONFIG_CHECKPOINT_RESTORE=y
-CONFIG_NAMESPACES=y
-CONFIG_USER_NS=y
-CONFIG_SCHED_AUTOGROUP=y
-CONFIG_BLK_DEV_INITRD=y
-CONFIG_EXPERT=y
-CONFIG_KALLSYMS_ALL=y
-CONFIG_BPF_SYSCALL=y
-CONFIG_USERFAULTFD=y
-# CONFIG_COMPAT_BRK is not set
-CONFIG_SLAB=y
-CONFIG_PROFILING=y
-CONFIG_KPROBES=y
-CONFIG_JUMP_LABEL=y
-CONFIG_CC_STACKPROTECTOR_STRONG=y
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-CONFIG_MODVERSIONS=y
-CONFIG_BLK_DEV_BSGLIB=y
-CONFIG_BLK_DEV_INTEGRITY=y
-CONFIG_BLK_DEV_THROTTLING=y
-CONFIG_PARTITION_ADVANCED=y
-CONFIG_CFQ_GROUP_IOSCHED=y
-CONFIG_SMP=y
-CONFIG_X86_X2APIC=y
-# CONFIG_X86_EXTENDED_PLATFORM is not set
-CONFIG_X86_INTEL_LPSS=y
-CONFIG_X86_AMD_PLATFORM_DEVICE=y
-CONFIG_IOSF_MBI=y
-CONFIG_HYPERVISOR_GUEST=y
-CONFIG_PARAVIRT=y
-CONFIG_PARAVIRT_SPINLOCKS=y
-CONFIG_GART_IOMMU=y
-CONFIG_CALGARY_IOMMU=y
-CONFIG_NR_CPUS=512
-CONFIG_SCHED_SMT=y
-CONFIG_PREEMPT_VOLUNTARY=y
-CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y
-CONFIG_MICROCODE_AMD=y
-CONFIG_NUMA=y
-CONFIG_NUMA_EMU=y
-CONFIG_MEMORY_HOTPLUG=y
-CONFIG_MEMORY_HOTREMOVE=y
-CONFIG_KSM=y
-CONFIG_DEFAULT_MMAP_MIN_ADDR=65536
-CONFIG_MEMORY_FAILURE=y
-CONFIG_TRANSPARENT_HUGEPAGE=y
-CONFIG_TRANSPARENT_HUGEPAGE_MADVISE=y
-CONFIG_FRONTSWAP=y
-CONFIG_MEM_SOFT_DIRTY=y
-CONFIG_ZSWAP=y
-CONFIG_ZBUD=y
-CONFIG_X86_INTEL_MPX=y
-CONFIG_EFI=y
-CONFIG_EFI_STUB=y
-CONFIG_EFI_MIXED=y
-CONFIG_KEXEC=y
-CONFIG_KEXEC_FILE=y
-CONFIG_KEXEC_VERIFY_SIG=y
-CONFIG_CRASH_DUMP=y
-CONFIG_RANDOMIZE_BASE=y
-CONFIG_LIVEPATCH=y
-CONFIG_HIBERNATION=y
-CONFIG_PM_DEBUG=y
-CONFIG_PM_ADVANCED_DEBUG=y
-# CONFIG_ACPI_AC is not set
-# CONFIG_ACPI_BATTERY is not set
-CONFIG_ACPI_BUTTON=m
-# CONFIG_ACPI_FAN is not set
-CONFIG_ACPI_DOCK=y
-# CONFIG_ACPI_THERMAL is not set
-CONFIG_ACPI_PCI_SLOT=y
-CONFIG_ACPI_HOTPLUG_MEMORY=y
-CONFIG_ACPI_BGRT=y
-CONFIG_ACPI_APEI=y
-CONFIG_ACPI_APEI_GHES=y
-CONFIG_ACPI_APEI_PCIEAER=y
-CONFIG_ACPI_APEI_MEMORY_FAILURE=y
-CONFIG_ACPI_EXTLOG=y
-CONFIG_SFI=y
-CONFIG_CPU_FREQ=y
-CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
-CONFIG_X86_INTEL_PSTATE=y
-CONFIG_INTEL_IDLE=y
-CONFIG_PCI_MMCONFIG=y
-CONFIG_PCIEPORTBUS=y
-CONFIG_HOTPLUG_PCI_PCIE=y
-CONFIG_PCI_REALLOC_ENABLE_AUTO=y
-CONFIG_PCI_IOV=y
-CONFIG_HOTPLUG_PCI=y
-CONFIG_HOTPLUG_PCI_ACPI=y
-CONFIG_HOTPLUG_PCI_CPCI=y
-CONFIG_IA32_EMULATION=y
-CONFIG_IA32_AOUT=y
-CONFIG_X86_X32=y
-CONFIG_NET=y
-CONFIG_PACKET=y
-CONFIG_UNIX=y
-CONFIG_XFRM_SUB_POLICY=y
-CONFIG_XFRM_MIGRATE=y
-CONFIG_INET=y
-CONFIG_IP_MULTICAST=y
-CONFIG_IP_ADVANCED_ROUTER=y
-CONFIG_IP_FIB_TRIE_STATS=y
-CONFIG_IP_MULTIPLE_TABLES=y
-CONFIG_IP_ROUTE_MULTIPATH=y
-CONFIG_IP_ROUTE_VERBOSE=y
-CONFIG_IP_MROUTE=y
-CONFIG_IP_MROUTE_MULTIPLE_TABLES=y
-CONFIG_IP_PIMSM_V1=y
-CONFIG_IP_PIMSM_V2=y
-CONFIG_SYN_COOKIES=y
-# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_INET_DIAG is not set
-CONFIG_TCP_CONG_ADVANCED=y
-# CONFIG_TCP_CONG_BIC is not set
-# CONFIG_TCP_CONG_WESTWOOD is not set
-# CONFIG_TCP_CONG_HTCP is not set
-CONFIG_TCP_MD5SIG=y
-CONFIG_IPV6_ROUTER_PREF=y
-CONFIG_IPV6_ROUTE_INFO=y
-CONFIG_IPV6_OPTIMISTIC_DAD=y
-CONFIG_IPV6_MIP6=y
-# CONFIG_INET6_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET6_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET6_XFRM_MODE_BEET is not set
-# CONFIG_IPV6_SIT is not set
-CONFIG_IPV6_MULTIPLE_TABLES=y
-CONFIG_IPV6_SUBTREES=y
-CONFIG_IPV6_MROUTE=y
-CONFIG_IPV6_MROUTE_MULTIPLE_TABLES=y
-CONFIG_IPV6_PIMSM_V2=y
-CONFIG_NETFILTER=y
-CONFIG_IP_NF_IPTABLES=m
-CONFIG_NET_SCHED=y
-CONFIG_NET_EMATCH=y
-CONFIG_NET_CLS_ACT=y
-CONFIG_DCB=y
-CONFIG_MPLS=y
-CONFIG_NET_MPLS_GSO=y
-CONFIG_NET_L3_MASTER_DEV=y
-CONFIG_CGROUP_NET_PRIO=y
-CONFIG_CGROUP_NET_CLASSID=y
-CONFIG_BPF_JIT=y
-CONFIG_LWTUNNEL=y
-# CONFIG_UEVENT_HELPER is not set
-CONFIG_DEVTMPFS=y
-# CONFIG_FIRMWARE_IN_KERNEL is not set
-CONFIG_CONNECTOR=y
-# CONFIG_PNP_DEBUG_MESSAGES is not set
-CONFIG_VIRTIO_BLK=y
-# CONFIG_SCSI_PROC_FS is not set
-CONFIG_BLK_DEV_SD=m
-CONFIG_CHR_DEV_SG=m
-CONFIG_SCSI_CONSTANTS=y
-CONFIG_SCSI_LOGGING=y
-CONFIG_SCSI_SCAN_ASYNC=y
-CONFIG_MEGARAID_NEWGEN=y
-CONFIG_SCSI_DH=y
-CONFIG_ATA=y
-# CONFIG_SATA_PMP is not set
-CONFIG_SATA_AHCI=y
-# CONFIG_ATA_SFF is not set
-CONFIG_MD=y
-CONFIG_NETDEVICES=y
-CONFIG_NET_FC=y
-CONFIG_VIRTIO_NET=y
-# CONFIG_NET_VENDOR_ARC is not set
-CONFIG_NET_TULIP=y
-# CONFIG_NET_VENDOR_SEEQ is not set
-CONFIG_INPUT_EVDEV=m
-CONFIG_MOUSE_PS2=m
-CONFIG_MOUSE_PS2_ELANTECH=y
-CONFIG_MOUSE_PS2_SENTELIC=y
-CONFIG_MOUSE_PS2_VMMOUSE=y
-CONFIG_INPUT_JOYSTICK=y
-CONFIG_INPUT_TABLET=y
-CONFIG_INPUT_TOUCHSCREEN=y
-CONFIG_INPUT_MISC=y
-CONFIG_INPUT_PCSPKR=m
-# CONFIG_SERIO_SERPORT is not set
-CONFIG_SERIO_RAW=m
-CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
-# CONFIG_LEGACY_PTYS is not set
-CONFIG_SERIAL_NONSTANDARD=y
-# CONFIG_DEVKMEM is not set
-CONFIG_SERIAL_8250=y
-# CONFIG_SERIAL_8250_DEPRECATED_OPTIONS is not set
-CONFIG_SERIAL_8250_CONSOLE=y
-CONFIG_SERIAL_8250_NR_UARTS=32
-CONFIG_SERIAL_8250_EXTENDED=y
-CONFIG_SERIAL_8250_MANY_PORTS=y
-CONFIG_SERIAL_8250_SHARE_IRQ=y
-CONFIG_SERIAL_8250_RSA=y
-# CONFIG_HW_RANDOM is not set
-CONFIG_HPET=y
-CONFIG_I2C=y
-CONFIG_I2C_I801=m
-CONFIG_SPI=y
-CONFIG_PINCTRL_BAYTRAIL=y
-CONFIG_PINCTRL_CHERRYVIEW=y
-CONFIG_PINCTRL_BROXTON=y
-CONFIG_PINCTRL_SUNRISEPOINT=y
-CONFIG_GPIO_SYSFS=y
-CONFIG_GPIO_INTEL_MID=y
-CONFIG_POWER_SUPPLY=y
-CONFIG_THERMAL_WRITABLE_TRIPS=y
-CONFIG_THERMAL_GOV_FAIR_SHARE=y
-CONFIG_THERMAL_GOV_BANG_BANG=y
-CONFIG_THERMAL_GOV_USER_SPACE=y
-# CONFIG_X86_PKG_TEMP_THERMAL is not set
-CONFIG_WATCHDOG=y
-CONFIG_ITCO_WDT=m
-CONFIG_ITCO_VENDOR_SUPPORT=y
-CONFIG_LPC_ICH=m
-CONFIG_AGP=y
-CONFIG_AGP_AMD64=y
-CONFIG_AGP_INTEL=y
-CONFIG_AGP_SIS=y
-CONFIG_AGP_VIA=y
-CONFIG_VGA_SWITCHEROO=y
-CONFIG_FB=y
-CONFIG_FIRMWARE_EDID=y
-CONFIG_FB_MODE_HELPERS=y
-CONFIG_FB_TILEBLITTING=y
-CONFIG_FB_VESA=y
-CONFIG_FB_EFI=y
-CONFIG_BACKLIGHT_LCD_SUPPORT=y
-# CONFIG_LCD_CLASS_DEVICE is not set
-CONFIG_BACKLIGHT_CLASS_DEVICE=y
-# CONFIG_BACKLIGHT_GENERIC is not set
-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
-CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
-# CONFIG_HID is not set
-CONFIG_NEW_LEDS=y
-CONFIG_LEDS_CLASS=y
-CONFIG_LEDS_TRIGGERS=y
-CONFIG_LEDS_TRIGGER_CPU=y
-CONFIG_ACCESSIBILITY=y
-CONFIG_A11Y_BRAILLE_CONSOLE=y
-CONFIG_EDAC=y
-# CONFIG_EDAC_DECODE_MCE is not set
-CONFIG_RTC_CLASS=y
-CONFIG_DMADEVICES=y
-CONFIG_VIRT_DRIVERS=y
-CONFIG_VIRTIO_PCI=y
-CONFIG_AMD_IOMMU=y
-CONFIG_AMD_IOMMU_V2=y
-CONFIG_INTEL_IOMMU=y
-CONFIG_INTEL_IOMMU_SVM=y
-# CONFIG_INTEL_IOMMU_DEFAULT_ON is not set
-CONFIG_IRQ_REMAP=y
-CONFIG_PM_DEVFREQ=y
-CONFIG_MEMORY=y
-CONFIG_GENERIC_PHY=y
-CONFIG_POWERCAP=y
-CONFIG_DMI_SYSFS=y
-CONFIG_ISCSI_IBFT_FIND=y
-CONFIG_EXT4_FS=m
-CONFIG_EXT4_FS_POSIX_ACL=y
-CONFIG_EXT4_FS_SECURITY=y
-CONFIG_FS_DAX=y
-CONFIG_FANOTIFY=y
-CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
-CONFIG_QUOTA=y
-CONFIG_QUOTA_NETLINK_INTERFACE=y
-CONFIG_AUTOFS4_FS=m
-CONFIG_PROC_KCORE=y
-CONFIG_TMPFS=y
-CONFIG_TMPFS_POSIX_ACL=y
-CONFIG_HUGETLBFS=y
-# CONFIG_EFIVAR_FS is not set
-CONFIG_NLS_DEFAULT="utf8"
-CONFIG_PRINTK_TIME=y
-CONFIG_BOOT_PRINTK_DELAY=y
-CONFIG_DYNAMIC_DEBUG=y
-CONFIG_STRIP_ASM_SYMS=y
-# CONFIG_UNUSED_SYMBOLS is not set
-# CONFIG_FRAME_POINTER is not set
-CONFIG_MAGIC_SYSRQ=y
-CONFIG_MAGIC_SYSRQ_DEFAULT_ENABLE=0x01b6
-CONFIG_PAGE_POISONING=y
-CONFIG_DEBUG_MEMORY_INIT=y
-CONFIG_LOCKUP_DETECTOR=y
-CONFIG_SCHEDSTATS=y
-CONFIG_SCHED_STACK_END_CHECK=y
-CONFIG_FTRACE_SYSCALLS=y
-CONFIG_TRACER_SNAPSHOT=y
-CONFIG_STACK_TRACER=y
-CONFIG_BLK_DEV_IO_TRACE=y
-CONFIG_UPROBE_EVENT=y
-CONFIG_MMIOTRACE=y
-CONFIG_MEMTEST=y
-CONFIG_STRICT_DEVMEM=y
-# CONFIG_X86_VERBOSE_BOOTUP is not set
-CONFIG_EARLY_PRINTK_EFI=y
-# CONFIG_DEBUG_RODATA_TEST is not set
-CONFIG_DEBUG_SET_MODULE_RONX=y
-CONFIG_OPTIMIZE_INLINING=y
-CONFIG_KEYS=y
-CONFIG_SECURITY_DMESG_RESTRICT=y
-CONFIG_SECURITY=y
-CONFIG_SECURITY_NETWORK_XFRM=y
-CONFIG_SECURITY_SELINUX=y
-CONFIG_SECURITY_TOMOYO=y
-CONFIG_SECURITY_APPARMOR=y
-CONFIG_SECURITY_YAMA=y
-CONFIG_IMA=y
-CONFIG_IMA_DEFAULT_HASH_SHA256=y
-CONFIG_IMA_APPRAISE=y
-CONFIG_DEFAULT_SECURITY_DAC=y
-# CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
-# CONFIG_CRYPTO_ECHAINIV is not set
-CONFIG_CRYPTO_CRC32C=y
-CONFIG_CRYPTO_CRC32C_INTEL=y
-CONFIG_CRYPTO_SHA256=y
-CONFIG_CRYPTO_DEV_CCP=y
-# CONFIG_CRYPTO_DEV_CCP_DD is not set
-# CONFIG_VIRTUALIZATION is not set
-# CONFIG_XZ_DEC_POWERPC is not set
-# CONFIG_XZ_DEC_IA64 is not set
-# CONFIG_XZ_DEC_ARM is not set
-# CONFIG_XZ_DEC_ARMTHUMB is not set
-# CONFIG_XZ_DEC_SPARC is not set
diff --git a/recipes-kernel/linux/linux-cip-common.inc b/recipes-kernel/linux/linux-cip-common.inc
index 8bd0f99..d45a3b0 100644
--- a/recipes-kernel/linux/linux-cip-common.inc
+++ b/recipes-kernel/linux/linux-cip-common.inc
@@ -26,4 +26,4 @@ SRC_URI += " \
SRC_URI_append = " ${@conditional("USE_CIP_KERNEL_CONFIG", "1", \
"git://gitlab.com/cip-project/cip-kernel/cip-kernel-config.git;protocol=https;destsuffix=cip-kernel-config;name=cip-kernel-config", \
"file://${KERNEL_DEFCONFIG}",d)}"
-SRCREV_cip-kernel-config ?= "f88ee1e75253104f975263cf4d0bddd557388197"
+SRCREV_cip-kernel-config ?= "db2085219b5f28ed7c3e0fbdf93b7867947958a8"
--
2.25.1


Re: CIP embedded platform Internet connection?

Akihiro Suzuki
 

Hi Mohammed,

 

> I realized that the configuration of the embedded platform and Hawkbit server may be specific for the SWUpdate demo. Suzuki-san, is that correct?

Yes. It is specific for the SWUpdate demo.

 

> is it OK if these parameters are in files or would you want them in a less permanent form (e.g. environment variables)?

If possible, I prefer the latter.

Current cip-sw-updates-demo repository has many inconvenient points.

If you have time, could you fix them?

 

Thanks,

Suzuki

 

From: cip-dev@... <cip-dev@...> On Behalf Of Mohammed Billoo
Sent: Thursday, July 30, 2020 9:32 AM
To: cip-dev@...
Subject: Re: [cip-dev] CIP embedded platform Internet connection?

 

Daniel,

 

Thanks for getting back. I realized that the configuration of the embedded platform and Hawkbit server may be specific for the SWUpdate demo. Suzuki-san, is that correct? If so, is it OK if these parameters are in files or would you want them in a less permanent form (e.g. environment variables)? The advantage of the latter would be that if I need to change the network configuration for my own set up (since my localhost external IP is different from what's in the BBB customization), I don't have to manage two different network configurations. I can set the appropriate environment variable (for example) and the build, if set up correctly, would pick up the environment variables and configure the BBB image correctly. Is there any strong conviction for either way?

 

Thanks 

Mohammed A Billoo
Founder
MAB Labs, LLC
www.mab-labs.com
201-338-2022

 

On Wed, Jul 29, 2020, 7:52 PM Daniel Sangorrin <daniel.sangorrin@...> wrote:

Hi Mohammed,

> -----Original Message-----
> From: cip-dev@... <cip-dev@...> On Behalf Of Mohammed Billoo
> This question stems from the thread titled "The security of NTP". If we do go with NTS, it looks like we're going to need an Internet
> connection to the embedded platform. Is that acceptable? The work that I've seen so far related to CIP SWUpdate has assumed that the
> Hawkbit server is on the local network. It isn't obvious if that has been an intentional decision (due to security requirements) or just to ease
> development.

There is nothing in CIP SWUpdate that assumes the Hawkbit server is on a local network.
Perhaps the README is using a local serve for demonstration purposes?

Thanks,
Daniel


--
Mohammed Billoo
MAB Labs, LLC
www.mab-labs.com


Re: [PATCH 3/3] README: Add steps to build cip-security image

Jan Kiszka
 

On 30.07.20 02:07, daniel.sangorrin@toshiba.co.jp wrote:
Hi Venkata-san
Maybe Jan didn't see your e-mail because he wasn't in the CC.

-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Venkata Pyla
Sent: Friday, July 24, 2020 3:58 PM
To: cip-dev@lists.cip-project.org
Subject: Re: [cip-dev] [PATCH 3/3] README: Add steps to build cip-security image

Hi Jan,

On Thu, Jul 23, 2020 at 04:10 PM, Jan Kiszka wrote:


On 21.07.20 10:16, Venkata Pyla wrote:
From: venkata <venkata.pyla@toshiba-tsip.com>

Signed-off-by: venkata <venkata.pyla@toshiba-tsip.com>
---
README.md | 10 ++++++++++
1 file changed, 10 insertions(+)

diff --git a/README.md b/README.md
index bbad1a0..b2c4166 100644
--- a/README.md
+++ b/README.md
@@ -36,6 +36,16 @@ card, run
dd
if=build/tmp/deploy/images/bbb/cip-core-image-cip-core-buster-bbb.wic.
img \
of=/dev/<medium-device> bs=1M status=progress

+## Building Security target images
+Building images for QEMU x86-64bit machine
+
+ ./kas-docker --isar build --target cip-core-image-security
kas.yml:board-qemu-amd64.yml
+
+Run the generated securiy images on QEMU (x86-64bit)
+
+ TARGET_IMAGE=cip-core-image-security ./start-qemu.sh amd64
+
+
## Community Resources

TBD
This patch is fine, but I'm missing 4/4: Add this image to CI (same
comment as I had on the MR on gitlab).
Adding cip security image to CI,
i need some suggestions to use the current format present in .gitlab-ci.yml

Currently i have the below problem for using script deploy-cip-core.sh:
1. image name formation in the script should have another variable
.../$IMG_PREFIX-cip-core-$RELEASE-$TARGET
where $IMG_PREFIX is default to "cip-core-image" if not specified
for security image it will be passed as 4th argument "cip-core-image-security"
2. currently scrit is expecting the image format in *.wic.img so,
for qemu i think we should have wks file to generate image with format .wic.img

or for this security image do we need to deploy it seperatley?
please guide me
Sometimes it is better to send a patch instead of trying to explain it with words.
I've replied on the deployment question already.

If there is a need for the security artifacts already, we need to enhance the deployment for that particular use case - but I doubt there is at this point, otherwise the series had carried CI in the first place.

Jan

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


Re: [isar-cip-core PATCH v3 1/6] kernel: add fat for qemu-amd64

Jan Kiszka
 

On 30.07.20 03:56, daniel.sangorrin@toshiba.co.jp wrote:
-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Jan Kiszka
Sent: Thursday, July 30, 2020 1:47 AM
To: cip-dev@lists.cip-project.org; Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: [cip-dev] [isar-cip-core PATCH v3 1/6] kernel: add fat for qemu-amd64

On 24.07.20 17:01, Quirin Gylstorff wrote:
From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

Add a fat configuration to access FAT Partitions on the qemu-amd64
target.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
recipes-kernel/linux/files/qemu-amd64_defconfig | 6 ++++++
1 file changed, 6 insertions(+)

diff --git a/recipes-kernel/linux/files/qemu-amd64_defconfig
b/recipes-kernel/linux/files/qemu-amd64_defconfig
index 7487152..5449317 100644
--- a/recipes-kernel/linux/files/qemu-amd64_defconfig
+++ b/recipes-kernel/linux/files/qemu-amd64_defconfig
@@ -351,3 +351,9 @@ CONFIG_CRYPTO_DEV_CCP=y
# CONFIG_XZ_DEC_ARM is not set
# CONFIG_XZ_DEC_ARMTHUMB is not set
# CONFIG_XZ_DEC_SPARC is not set
+CONFIG_MSDOS_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_NLS_ASCII=y
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_UTF8=y
Taking that for now, but we should quickly move that defconfig into cip-kernel-config. I'm not sure if there is anything for qemu already.
Could you check an propose our defconfig for it?
I confirmed that cip-kernel-config's qemu config boots correctly with isar-cip-core's start_qemu.sh.
Shall i prepare a patch that removes the local one and picks up the one from cip-kernel-config.
That would be good.

If needed, Quirin, please patch cip-kernel-config directly for these extra switches.

Jan

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


CIP IRC weekly meeting today

masashi.kudo@cybertrust.co.jp <masashi.kudo@...>
 

Hi all,

Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today.

*Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting from the first week of Apr. according to TSC meeting*
https://www.timeanddate.com/worldclock/meetingdetails.html?year=2020&month=7&day=30&hour=9&min=0&sec=0&p1=224&p2=179&p3=136&p4=37&p5=241&p6=248

USWest USEast UK DE TW JP
02:00 05:00 10:00 11:00 17:00 18:00

Channel:
* irc:chat.freenode.net:6667/cip

Last meeting minutes:
https://lore.kernel.org/cip-dev/OSAPR01MB23857705B82D0D163B5E5211B7770@OSAPR01MB2385.jpnprd01.prod.outlook.com/T/#m873e67bf005078f86fe9f659682614def4a448a6

Agenda:

* Action item
1. Combine root filesystem with kselftest binary - iwamatsu
2. Post LTP results to KernelCI - patersonc
3. Email Kernel team/cip-dev about patchwork usage - patersonc
Old AI "Issues to be fixed for swupdate "copyright correction and salsa CI testing" - iwamatsu" was taken care by SZ-san and was closed last week.

* Kernel maintenance updates
* Kernel testing
* Software update
* CIP Security
* AOB

The meeting will take 30 min, although it can be extended to an hour if it makes sense and those involved in the topics can stay. Otherwise, the topic will be taken offline or in the next meeting.

Best regards,
--
M. Kudo
Cybertrust Japan Co., Ltd.


Re: [isar-cip-core PATCH v3 1/6] kernel: add fat for qemu-amd64

Daniel Sangorrin <daniel.sangorrin@...>
 

-----Original Message-----
From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On Behalf Of Jan Kiszka
Sent: Thursday, July 30, 2020 1:47 AM
To: cip-dev@lists.cip-project.org; Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: [cip-dev] [isar-cip-core PATCH v3 1/6] kernel: add fat for qemu-amd64

On 24.07.20 17:01, Quirin Gylstorff wrote:
From: Quirin Gylstorff <quirin.gylstorff@siemens.com>

Add a fat configuration to access FAT Partitions on the qemu-amd64
target.

Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
---
recipes-kernel/linux/files/qemu-amd64_defconfig | 6 ++++++
1 file changed, 6 insertions(+)

diff --git a/recipes-kernel/linux/files/qemu-amd64_defconfig
b/recipes-kernel/linux/files/qemu-amd64_defconfig
index 7487152..5449317 100644
--- a/recipes-kernel/linux/files/qemu-amd64_defconfig
+++ b/recipes-kernel/linux/files/qemu-amd64_defconfig
@@ -351,3 +351,9 @@ CONFIG_CRYPTO_DEV_CCP=y
# CONFIG_XZ_DEC_ARM is not set
# CONFIG_XZ_DEC_ARMTHUMB is not set
# CONFIG_XZ_DEC_SPARC is not set
+CONFIG_MSDOS_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_NLS_ASCII=y
+CONFIG_NLS_CODEPAGE_437=y
+CONFIG_NLS_ISO8859_1=y
+CONFIG_NLS_UTF8=y
Taking that for now, but we should quickly move that defconfig into cip-kernel-config. I'm not sure if there is anything for qemu already.
Could you check an propose our defconfig for it?
I confirmed that cip-kernel-config's qemu config boots correctly with isar-cip-core's start_qemu.sh.
Shall i prepare a patch that removes the local one and picks up the one from cip-kernel-config.

Thanks,
Daniel


Re: [PATCH 4.4.y-cip] ARM: dts: iwg22d-sodimm: Enable touchscreen

Nobuhiro Iwamatsu
 

Hi,

-----Original Message-----
From: Biju Das [mailto:biju.das.jz@bp.renesas.com]
Sent: Wednesday, July 29, 2020 7:56 PM
To: cip-dev@lists.cip-project.org; iwamatsu nobuhiro(岩松 信洋 □SWC◯ACT)
<nobuhiro1.iwamatsu@toshiba.co.jp>; Pavel Machek <pavel@denx.de>
Cc: Chris Paterson <chris.paterson2@renesas.com>; Biju Das <biju.das.jz@bp.renesas.com>; Prabhakar Mahadev Lad
<prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: [PATCH 4.4.y-cip] ARM: dts: iwg22d-sodimm: Enable touchscreen

From: Marian-Cristian Rotariu <marian-cristian.rotariu.rb@bp.renesas.com>

commit 99ae78f1fc3a73c88fe726c676ae963ce722bf20 upstream.

In one of the iWave-G22D development board variants, called Generic SODIMM
Development Platform, we have an LCD with touchscreen. The resistive touch
controller, STMPE811 is on the development board and is connected through
the i2c5 of the RZ-G1E.

Additionally, this controller should generate an interrupt to the CPU and
it is connected through GPIO4,4 to the GIC.

Touch was tested with one of our iW-RainboW-G22D-SODIMM RZ/G1E development
platforms.

More details on the iWave website:
https://www.iwavesystems.com/rz-g1e-sodimm-development-kit.html

Signed-off-by: Marian-Cristian Rotariu <marian-cristian.rotariu.rb@bp.renesas.com>
Link: https://lore.kernel.org/r/1583336650-25848-1-git-send-email-marian-cristian.rotariu.rb@bp.renesas.com
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
There seems to be no issue with this patch, but we also need to update defcofnig.
If there is no other objection, I will apply this.

Best regards,
Nobuhiro


---
arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts | 33 +++++++++++++++++++++
1 file changed, 33 insertions(+)

diff --git a/arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts b/arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts
index 1e331d1e414b..5cd989556b60 100644
--- a/arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts
+++ b/arch/arm/boot/dts/r8a7745-iwg22d-sodimm.dts
@@ -149,6 +149,39 @@
status = "okay";
clock-frequency = <400000>;

+ stmpe811@44 {
+ compatible = "st,stmpe811";
+ reg = <0x44>;
+ interrupt-parent = <&gpio4>;
+ interrupts = <4 IRQ_TYPE_LEVEL_LOW>;
+
+ /* 3.25 MHz ADC clock speed */
+ st,adc-freq = <1>;
+ /* ADC converstion time: 80 clocks */
+ st,sample-time = <4>;
+ /* 12-bit ADC */
+ st,mod-12b = <1>;
+ /* internal ADC reference */
+ st,ref-sel = <0>;
+
+ stmpe_touchscreen {
+ compatible = "st,stmpe-ts";
+ /* 8 sample average control */
+ st,ave-ctrl = <3>;
+ /* 7 length fractional part in z */
+ st,fraction-z = <7>;
+ /*
+ * 50 mA typical 80 mA max touchscreen drivers
+ * current limit value
+ */
+ st,i-drive = <1>;
+ /* 1 ms panel driver settling time */
+ st,settling = <3>;
+ /* 5 ms touch detect interrupt delay */
+ st,touch-det-delay = <5>;
+ };
+ };
+
sgtl5000: codec@a {
compatible = "fsl,sgtl5000";
#sound-dai-cells = <0>;
--
2.17.1


Re: CIP embedded platform Internet connection?

Mohammed Billoo <mab@...>
 

Daniel,

Thanks for getting back. I realized that the configuration of the embedded platform and Hawkbit server may be specific for the SWUpdate demo. Suzuki-san, is that correct? If so, is it OK if these parameters are in files or would you want them in a less permanent form (e.g. environment variables)? The advantage of the latter would be that if I need to change the network configuration for my own set up (since my localhost external IP is different from what's in the BBB customization), I don't have to manage two different network configurations. I can set the appropriate environment variable (for example) and the build, if set up correctly, would pick up the environment variables and configure the BBB image correctly. Is there any strong conviction for either way?

Thanks 

Mohammed A Billoo
Founder
MAB Labs, LLC
www.mab-labs.com
201-338-2022

On Wed, Jul 29, 2020, 7:52 PM Daniel Sangorrin <daniel.sangorrin@...> wrote:
Hi Mohammed,

> -----Original Message-----
> From: cip-dev@... <cip-dev@...> On Behalf Of Mohammed Billoo
> This question stems from the thread titled "The security of NTP". If we do go with NTS, it looks like we're going to need an Internet
> connection to the embedded platform. Is that acceptable? The work that I've seen so far related to CIP SWUpdate has assumed that the
> Hawkbit server is on the local network. It isn't obvious if that has been an intentional decision (due to security requirements) or just to ease
> development.

There is nothing in CIP SWUpdate that assumes the Hawkbit server is on a local network.
Perhaps the README is using a local serve for demonstration purposes?

Thanks,
Daniel


--
Mohammed Billoo
MAB Labs, LLC
www.mab-labs.com

2001 - 2020 of 7073