ymz5

The initiative originates in Europe, thus it's European. It aims at solving very concrete problems, particularly about running RTOSes used in industrial computing, and efficient resource partitioning. It invites industrial companies to join.

Or what exactly was your question about?

What "that approach"? In the scope of the initiative, we are talking about full isolation of operating systems (which is possible with the hypervisor). I still don't understand why are you offering me to read about L4 and RT-Linux.

(QSOE/L does use seL4 as one of its possible kernels. But I guess you also haven't noticed this, because, perhaps, you don't care.)

Excuse me, but what Barabanov, Yodaiken and all the stuff you mentioned have to do with the subject?

Have you noticed that Linux on the diagram is a general-purpose OS, used for non-critical tasks? Or, refusing to watch the video, you refuse also to see what's actually depicted on the page?

> it's been working since the 01990s

What's been working since the "01990s"? What hypervisor in 1990s drove real-time OSes on industrial computers alongside general-purpose OSes, providing full resource isolation?

> ERICI's plan to run Linux under a real-time hypervisor...

Why plan? It's working right now, alongside QSOE/N. Resources nicely partitioned: graphics controller and UFS storage for Linux; NVMe, Ethernet UART for QSOE. Please see the demonstration video.

> ... the device tree blob could/would be embedded in the same package as this HFI firmware

Why "could/would"? It is part of the firmware, now. HFI BIOS is U-Boot + VideoBIOS + Set-Up program. Its job is to initialize your hardware (video controller included) and start your boot loader (EFI program), just like in a PC.

> ... even if the main NAND/emmc/SSD hosting the OS is wiped out

There is [almost] always the possibility of recovery. I have three RISC-V systems, and each of them cannot be "bricked": * X-Modem for VF2; * SD-card boot for Unmatched; * fastboot (Android) protocol for the K3

> on PCs, there is usually a NOR flash that hosts the BIOS/UEFI.

Same on Unmatched, for example: you may store HFI BIOS in NOR (boots very fast!), or on your SD card (boots slow, only 81 KB/sec). What to boot from is selected by DIP switches. Similar mechanism on VF2 too.

> Where is Siemens and Bosch these days…

Hopefully they praise the initiative. ;-)

It is supposed to be a sturdy industrial computer with a RVA23-capable SoC inside, capable of running two or more OSes simultaneously. At least one of those OSes must be a hard-real-time OS, used e.g. in control or robot tasks.

> Why the emphasis on RVA23?

Easy. In fact, the emphasis will be on RVA23 _and_ on working IOMMU hardware. This is needed for hardware resource isolation between operating systems running on the hypervisor.

RVA23 is mandatory for Ubuntu, for example. So the requirement is not new at all.

No, I did not. Are you looking at some other page?

Would be happy to port the stack to a RVA23-capable system from Cortus, Codasip or any other European firm! Once the board is available, of course.

Author here. Happy to answer technical questions: about HFI BIOS, partitioning hypervisor (gRouvr), QSOE RTOS.

I hope that leading European industrial computer manufacturers notice the initiative and join -- or at least start evaluating the possibility to use RVA23 SoCs in their devices. Yes, currently only Chinese vendors can provide such chips, but the world is changing fast.

Have you noticed the words "non-commercial" at the bottom of the page?

The random dude is not looking for funding.