Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-09-19 04:24:53 -04:00
Code Issues Projects Releases Packages Wiki Activity

Refactor links in order to obey the new convention rule

Browse source
This commit is contained in:
Tobias Killer 2021-04-11 01:00:19 +02:00
parent 5047127350
commit 9415119edc
No known key found for this signature in database
GPG key ID: 2DA5EF6F6E40B328
3 changed files with 4 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

4
user/hardware/certified-hardware.md
View file

@ -63,7 +63,7 @@ Another important requirement is that Qubes-certified hardware should run only *
The only exception is the use of (properly authenticated) CPU-vendor-provided blobs for silicon and memory initialization (see [Intel FSP](https://firmware.intel.com/learn/fsp/about-intel-fsp)) as well as other internal operations (see [Intel ME](https://www.apress.com/9781430265719)).
However, we specifically require all code used for and dealing with the System Management Mode (SMM) to be open-source.
While we [recognize](https://blog.invisiblethings.org/papers/2015/x86_harmful.pdf) the potential problems that proprietary CPU-vendor code can cause, we are also pragmatic enough to realize that we need to take smaller steps first, before we can implement even stronger countermeasures such as a [stateless laptop].
While we [recognize](https://blog.invisiblethings.org/papers/2015/x86_harmful.pdf) the potential problems that proprietary CPU-vendor code can cause, we are also pragmatic enough to realize that we need to take smaller steps first, before we can implement even stronger countermeasures such as a [stateless laptop](https://blog.invisiblethings.org/papers/2015/state_harmful.pdf).
A switch to open source boot firmware is one such important step.
To be compatible with Qubes OS, the BIOS must properly expose all the VT-x, VT-d, and SLAT functionality that the underlying hardware offers (and which we require).
Among other things, this implies **proper DMAR ACPI table** construction.
@ -94,5 +94,3 @@ While we are willing to troubleshoot simple issues, we will need to charge a con
If you are interested in having your hardware certified, please [contact us](mailto:business@qubes-os.org).
[stateless laptop]: https://blog.invisiblethings.org/2015/12/23/state_harmful.html
[stateless laptop]: https://blog.invisiblethings.org/papers/2015/state_harmful.pdf