From: Laurent Pinchart <laurent.pinchart+renesas@...> commit bf7149f34241dcd6c95ea76b2b5ab4ff33f1c9b9 upstream. Instead of parsing the panel device tree node manually, use the panel API

Document the Emerging Display Technology Corp. (EDT) ETM043080DH6-GP display, which is a 480x272 4.3" TFT display with capacitive touchscreen. This patch is based on the upstream commit

From: Eric Anholt <eric@...> commit 0b27c02a7f1c697694f2ad6d6517e7dbf9ecfa39 upstream. Right now exynos is exposing DPI as a TMDS encoder and VGA connector, which seems rather misleading.

Add LCD Panel support for iWave RZ/G1E board based on r8a7745 SoC. Backporting the panel patch as it is, requires drm bridge Api changes, which is not present at 4.4 kernel. So used the 4.4 rm

From: Fabrizio Castro <fabrizio.castro@...> commit a630a6121bef3e9598482a49eda6b1fa715385d6 upstream. The iwg20d comes with an LCD panel from Emerging Display Technologies Corporation

Still no CI for this. You can send that separately on top, the series looks fine otherwise. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

Hi, 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

Cool. I'll check out NTS and I'll just respond in this group with silly questions as I stumble along (I'm new to CIP and am not a security expert at all). -- Mohammed Billoo MAB Labs,

Hi Mohammed

Daniel, Thanks for pointing that out. Since CIP is reliant on available packages on particular versions of Debian, would the process/workflow then be to wait for tlsdate to be available in Buster and

Test - please ignore. Thanks, Neal Caidin Linux Foundation (sent from a personal account)

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

From: Venkata Pyla <venkata.pyla@...> Use 'TARGET_IMAGE' to pick respective image file when starting qemu by default 'TARGET_IMAGE' uses "cip-core-image". to pick different target image

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

From: Venkata Pyla <venkata.pyla@...> Patch series for Security changes for IEC-62443-4-2 evaluation Kazuhiro Hayashi (1): cip-security: Add packages for IEC-62443-4-2

Daniel, Pavel: Thanks for the feedback. Is tlsdate a better alternative (https://github.com/ioerror/tlsdate/)? The only caveat if using tlsdate (or any sort of time mechanism that relies on a

FYI Kind regards, Chris

Hello, During the last CIP Core meeting we discussed about license compliance for CIP core image releases. In particular, we talked about how to make sure that users can get exactly the same source

Hi Jan, Patches give you greater visibility (all cip-dev members), but I can see some benefits in using MRs as well: * merge when the pipeline succeeds * map issues with the patches that close them *