From 89f81ecf82d1dcd5ee912b8b9381027be6d8ab65 Mon Sep 17 00:00:00 2001 From: qm <3440586+qm@users.noreply.github.com> Date: Fri, 4 Oct 2024 10:27:11 -0400 Subject: [PATCH] added sublists for better rst conversion formatting --- user/hardware/system-requirements.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/user/hardware/system-requirements.md b/user/hardware/system-requirements.md index ffe39f7c..63aabd50 100644 --- a/user/hardware/system-requirements.md +++ b/user/hardware/system-requirements.md @@ -122,7 +122,7 @@ We recommend consulting these resources when selecting hardware for Qubes OS: 2. The user's OEM, ODM, or MB to provide a suitable BIOS or (U)EFI update for the user's system. - Historically, AMD has often been slow to complete step (1), at least for its + - Historically, AMD has often been slow to complete step (1), at least for its client (as opposed to server) platforms. In some cases, AMD has made fixes available for its server platforms very shortly after a security embargo was lifted, but it did not make fixes available for client platforms facing the @@ -132,10 +132,10 @@ We recommend consulting these resources when selecting hardware for Qubes OS: new CPU vulnerabilities across its supported platforms very shortly after security embargoes have been lifted. - Step (2) varies by vendor. Many vendors fail to complete step (2) at all, + - Step (2) varies by vendor. Many vendors fail to complete step (2) at all, while some others take a very long time to complete it. - The bottom line is that Qubes OS **can** run on AMD systems, and the Qubes and + - The bottom line is that Qubes OS **can** run on AMD systems, and the Qubes and Xen security teams do their best to provide security support for AMD systems. However, without the ability to ship microcode updates, there is only so much they can do.