"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.
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.
@nineteen999 makes a valid point, but I don't think this is a case of protectionism.
From what I can tell, it's more about RH's ludicrous licensing policy and the economic practicality of using something "application binary compatible." (•_• )
10 comments
[ 6.2 ms ] story [ 40.7 ms ] threador is it the redhat version of AGL https://www.automotivelinux.org/ which is more for the infotainment.
"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...
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.
From what I can tell, it's more about RH's ludicrous licensing policy and the economic practicality of using something "application binary compatible." (•_• )