not sure if this is for infotainment, or the real time control of the car? or just for the autonomous computing? it's pretty vague to me.
or is it the redhat version of AGL https://www.automotivelinux.org/ which is more for the infotainment.
It says "mixed-criticality"
"Mixed-criticality essentially means one chip is running two pieces of software that require disparate safety levels. An example would be a single chip that controls both radio volume and electric steering controls. A failure of audio controls is annoying — while a failure of steering controls is dangerous, possibly even life-threatening."[0]
It says they're working on ISO 26262 Automotive Safety Integrity Level B (ASIL-B) which from[0] says - "medium-risk" for failures e.g. headlights or rear-camera.
[0] https://blogs.blackberry.com/en/2022/09/why-mixed-criticalit...
Do you know if this is common in automotive?
In medical devices that follow IEC62304 we usually try to physically segregate code that are at different safety classifications.
[edit] after RTFM'ing I see why they do it.
Iso 26262 is very common in automotive, it affects powertrain and steering components
FWIW - it happens in aerospace - ARINC 651/653
I'm really not sure how to feel about the fact that, meanwhile in Germany, RH has made its way onto the non-preferred vendor list of at least one large enterprise in the automotive industry.
Why?
Possibly to favour SuSE which is a German-based RH competitor (and which has a much longer history in the automotive industry from what I have read).