Hi all As we move forward with the Safety Arch WG activities we will start looking at specific architectures/demos/HW components. As I want to avoid to have random people to look at our material I wou

Hi All I am following up on my AR. I got clearance from Intel to share a template used internally for requirements definition and tracking. As we move along with our WG activity we may use this templa

Hi all I spent some time looking at the patch below and at the associated driver https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/media/platform/vsp1?h=v5.5.9&id=5e824f9

Hi all Following up on last week meeting tomorrow Haraki san will present the details of Suzuki’s PoC demo with some details on the CRC error check. If there is time left Maurizio will give an overvie

Reminder: ELISA Safety-Architecture Weekly Meeting When: Tuesday, 24 March 2020, 1:00pm to 2:00pm, (GMT+00:00) UTC View Event Organizer: myu@... myu@... Description: ────────── ELISA Project is inviti

Hi all Many Thanks for joining. We have the following action items: [A.I.] Ito san and Haraki san to tell if they can disclose info on the DISCOM to write the CRC exception handling driver in Linux [A

Hi All Sorry for the late agenda. Today we will discuss about option B (EDAC safety application) as we are still waiting for feedbacks from Renesas with respect to the disclosure of HW details of the

Hi all Many thanks for the good discussion today. We finally have a plan for short term next steps (copied inline below): 1) [Gab] Build a Github repo to store the safety app 2) [Gab] Define a safety

Reminder: ELISA Safety-Architecture Weekly Meeting When: Tuesday, 7 April 2020, 12:00pm to 1:00pm, (GMT+00:00) UTC View Event Organizer: myu@... myu@... Description: ────────── ELISA Project is inviti

Hi All I have created a github repo to store code for the Safety Arch WG. I have created a skeleton for the dummy edac app and Makefile. Please see: https://github.com/elisa-tech/Safety_Architecture_W

Hi All In the last meeting I had the AR to share a template for the safety analyses; hence I am sharing an FMEA template proposal (see below). Pls review it and send your comments; also it would be go

Hi all Tomorrow I think we have few topics: 1) Any Update about the possibility of sharing enough details of DISCOM HW to write a Kernel driver 2) Development of a Dummy Edac driver that is platforms

Hi all Thank you so much for joining despite the zoom technical challenges (it seems that you need a Zoom account now; FYI I’ve done it in a quite straightforward way by using my Google account to cre

ELISA Community, We have made a change in the Zoom setting to minimize the risk of uninvited participants joining our community meetings. Starting from this week, only Zoom authenticated users will be

Hi everyone, seems zoom doesn’t like me anymore and won’t let me join the call on grounds of this meeting being for authorized people only. Is ist just me, or is there a general problem? Best Regards

Create the base skeleton for a dummy edac module. This module creates a dummy edac memory controller that is not bound to any real HW. Signed-off-by: Gabriele Paoloni <gabriele.paoloni@...> --- driver

Adding the sysfs attributes that are used to inject errors from user space into the dummy module Signed-off-by: Gabriele Paoloni <gabriele.paoloni@...> --- drivers/edac/edac_inject_dummy.c | 115 +++++

Adding the EDAC error checking function. The function goes over the dummy errors set by sysfs to see if any has happened and eventually calls the mci error handling routine Signed-off-by: Gabriele Pao

Updating MAINTAINERS file to add Gabriele Paoloni as maintainer of edac_inject_dummy.c Signed-off-by: Gabriele Paoloni <gabriele.paoloni@...> --- MAINTAINERS | 6 ++++++ 1 file changed, 6 insertions(+)

Reminder: ELISA Safety-Architecture Weekly Meeting When: Tuesday, 14 April 2020, 12:00pm to 1:00pm, (GMT+00:00) UTC View Event Organizer: myu@... myu@... Description: ────────── ELISA Project is invit