From: Laurent Pinchart <laurent.pinchart+renesas@...> commit 968328496b0fbee42abb6fae98ba0dc720bda977 upstream. The DRM core and DU driver guarantee that the LVDS bridge will not

From: Sean Paul <seanpaul@...> commit 5ade071ba13e3bb24e3a9d5f8d6a3cf145deeb18 upstream. This patch adds atomic variants for all of pre_enable/enable/disable/post_disable bridge functions.

Add RZ/G2E Dual LVDS display support. All patches in this series are cherry-picked from upstream kernel. Fabrizio Castro (7): drm: rcar-du: lvds: Improve identification of panels drm: of: Add

Nobuhiro, is something missing from your perspective in Daniels approach? If not, I'd like to have one patch that takes us to that level. By now, I think an opt-testtools.yml is better (an "option",

Hi Jan

That would confuse me now: What creating a separate test image first, just to remove it again? Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded

________________________________________ Sent: Wednesday, July 22, 2020 3:44 PM To: cip-dev@...; sangorrin daniel(サンゴリン ダニエル □ＳＷＣ◯ＡＣＴ); iwamatsu

"Having ... as well." Does this obsolete https://gitlab.com/cip-project/cip-core/isar-cip-core/-/merge_requests/7, where I just commented on? Wording: It's not a testing layer, it's "test packages",

Hi Kent, Let me check if we can use the cip-kernel-config version on ISAR and remove the one in isar-cip-core. I will also add nftables as a fragment to isar-cip-core until you tell me that it needs

Hi Jan, Sorry, I failed to put you in the Cc when I sent this patch. There are also 3 patches from Venkata-san on the cip-dev mailing list (sent yesterday) Apart from that there are some merge

Hi Pavel, Thanks for the feedback. Yes, Will do. Regards, Biju Renesas Electronics Europe GmbH, Geschaeftsfuehrer/President: Carsten Jauch, Sitz der Gesellschaft/Registered office: Duesseldorf,

Hi! I see it is already pushed, thank you! Biju, the first patch seems like a bugfix suitable for -stable. Can you send it to Greg (etc) for inclusion? Best regards, Pavel -- DENX

having an opt-tests layer makes it easier to see what tests are installed, and allows creating images without them as well Signed-off-by: Daniel Sangorrin <daniel.sangorrin@...> ---

I see. Thank you, Daniel. But, I'm wondering why conf/machine/qemu-amd64.conf doesn't define USE_CIP_KERNEL_CONFIG = "1". Do you have any information for this, Dinesh or Venkata? I think we should

From: venkata <venkata.pyla@...> Signed-off-by: venkata <venkata.pyla@...> --- README.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README.md

From: venkata <venkata.pyla@...> if 'TARGET_IMAGE' variable is not set then it pick "cip-core-image", to pick different target image set the 'TARGET_IMAGE' variable as below e.g:

From: Kazuhiro Hayashi <kazuhiro3.hayashi@...> Identified security packages are added to the target image and that will be used for IEC-62443-4-2 evaluation Signed-off-by: Kazuhiro Hayashi

Hi Kent, The configuration should go to https://gitlab.com/cip-project/cip-kernel/cip-kernel-config not isar-cip-core. isar-cip-core and deby share cip-kernel-config configuration

Hi Pavel and Nobuhiro, Thanks for the feedback.

Hi, The security working group need to use "nftables", and it requires to add the below kernel configs to work. Before merging to the master branch of "isar-cip-core", would you kindly review to