From 804677a5f7649f9b78cced7381d0b1029b5be680 Mon Sep 17 00:00:00 2001 From: Syndamia Date: Mon, 26 Feb 2024 09:39:01 +0200 Subject: (tutorials/fqc) Converted post to MEL format --- src/tutorials/fix-qc-timeout/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/tutorials/fix-qc-timeout/index.md b/src/tutorials/fix-qc-timeout/index.md index fe93cdf..9b02a48 100644 --- a/src/tutorials/fix-qc-timeout/index.md +++ b/src/tutorials/fix-qc-timeout/index.md @@ -37,7 +37,7 @@ libata.force=3.01:nodmalog ## Explanation -&&important The following is how I understand the issue, but I did not find definitive proof thats exactly what happens. +&:important The following is how I understand the issue, but I did not find definitive proof thats exactly what happens. Take this section with a grain of salt. A harddrive can support [dma transfers](https://en.wikipedia.org/wiki/Direct_memory_access), normally the CPU would handle data transfer from the harddrive to the system memory (RAM), meaning it asks for a bit of data, waits, when the data comes, puts it in memory, then asks for next bit and so on. -- cgit v1.3.1-23-gd82d