Thank You.
mail-archive search summary
So far searched using
https://www.mail-archive.com/search?q=%22System+Management+Mode%22&l=qubes-users%40googlegroups.com
https://www.mail-archive.com/search?q=%22System+Management+Mode%22&l=qubes-devel%40googlegroups.com
https://www.mail-archive.com/search?q=SMM&l=qubes-users%40googlegroups.com
https://www.mail-archive.com/search?q=SMM&l=qubes-devel%40googlegroups.com
Feel like using dictionary without knowing spelling. Any more pointers? I will dig more and update when find and understand more.
FWIW my opinion is hardware certification rationale for open-source SMM requirement is not easy to discover (at least for me ).
Did find this qubes-users discussion thought provoking and possibly relevant.
@tasket in qubes-users post say
“The biggest problem I see is peoples’ willingness to go along with what is becoming a tradition of anti-competition. Whatever logical fallacies are put forward to make it seem palatable with CPUs will also undermine user motivations in other areas.”
and in followup say
“TBH, I’m not exactly sure why, from a consumer standpoint, open firmware must be a prerequisite when the hardware itself is closed.”
@Insurgo responds
“Because the firmware controls the hardware until open source hardware exists altogether.”
“And the question that arises is: What is Open Source Firmware nowadays?”
tasket reply includes
"Open firmware is becoming more of a long-term goal that we can acheive alongside open hardware. Clearly its not working out too well with closed hardware, and the closed firmware might as well be considered a part of the hardware, IMO. "
Not want to misrepresent other’s idea so mentioning.
My conclusion: Understanding hardware tradeoffs is hard.
Assumption: Creating Qubes hardware certification requirements is even harder.