summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrancis Rowe <info@gluglug.org.uk>2015-09-19 12:49:35 (EDT)
committer Francis Rowe <info@gluglug.org.uk>2015-09-19 12:49:35 (EDT)
commit987bac5cf0d73a8a99ff9083135482e1c17fe2d2 (patch)
tree367023d133d32f2c0cdc44da40c2ddbeae5ad436
parent2f1c0d94673179df533c2150424d3cdf469eed34 (diff)
downloadlibreboot.org-987bac5cf0d73a8a99ff9083135482e1c17fe2d2.zip
libreboot.org-987bac5cf0d73a8a99ff9083135482e1c17fe2d2.tar.gz
libreboot.org-987bac5cf0d73a8a99ff9083135482e1c17fe2d2.tar.bz2
typo fix
-rw-r--r--site/faq/index.php2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/faq/index.php b/site/faq/index.php
index d5eac9c..158e22c 100644
--- a/site/faq/index.php
+++ b/site/faq/index.php
@@ -639,7 +639,7 @@
&lt;CareBear\&gt;if a DMA Setup FIS is sent first, with the Auto-Activate bit set, then it is already set up, and the drive can initiate DMA<br/>
&lt;CareBear\&gt; &quot;First party DMA is a superset capability not neccessarily supported by legacy mode devices or legacy mode device drivers but essential for accommodating future capabilities.&quot; translation: if the problem isn't already there it will be shortly<br/>
&lt;CareBear\&gt; &quot;Upon receiving a DMA Setup, the receiver of the FIS shall validate the received DMA Setup request&quot; - ie. the host is supposed to validate, but hey, maybe there's a bug there..<br/>
- &lt;CareBear\&gt; &quot;The specific implementation of the buffer identifier and buffer/address validation is not specified.&quot; - so noone will actually bother
+ &lt;CareBear\&gt; &quot;The specific implementation of the buffer identifier and buffer/address validation is not specified.&quot; - so noone will actually bother<br/>
&lt;Basstard`&gt; &quot;the receiver of the FIS&quot;<br/>
&lt;CareBear\&gt; in the case we're considering that's the host controller hardware in the chipset and/or the kernel driver<br/>
&lt;CareBear\&gt; most likely kernel driver<br/>