diff options
| -rw-r--r-- | site/faq/index.php | 2 |
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 @@ <CareBear\>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/> <CareBear\> "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." translation: if the problem isn't already there it will be shortly<br/> <CareBear\> "Upon receiving a DMA Setup, the receiver of the FIS shall validate the received DMA Setup request" - ie. the host is supposed to validate, but hey, maybe there's a bug there..<br/> - <CareBear\> "The specific implementation of the buffer identifier and buffer/address validation is not specified." - so noone will actually bother + <CareBear\> "The specific implementation of the buffer identifier and buffer/address validation is not specified." - so noone will actually bother<br/> <Basstard`> "the receiver of the FIS"<br/> <CareBear\> in the case we're considering that's the host controller hardware in the chipset and/or the kernel driver<br/> <CareBear\> most likely kernel driver<br/> |