diff options
| author | Jeff Garzik <jeff@garzik.org> | 2007-02-26 01:26:06 -0500 |
|---|---|---|
| committer | Jeff Garzik <jeff@garzik.org> | 2007-04-28 14:15:55 -0400 |
| commit | d88184fb2348a50f7c34f5d49a901c875b2e0114 (patch) | |
| tree | 83993038a7525f6b61aea8f76ea38ddb96325a2f /net | |
| parent | 43727fbc753c63f9d2764c56467303698cc52c14 (diff) | |
| download | linux-3.10-d88184fb2348a50f7c34f5d49a901c875b2e0114.tar.gz linux-3.10-d88184fb2348a50f7c34f5d49a901c875b2e0114.tar.bz2 linux-3.10-d88184fb2348a50f7c34f5d49a901c875b2e0114.zip | |
[libata] sata_mv: clean up DMA boundary issues, turn on 64-bit DMA
The chips covered by sata_mv have a 32-bit DMA boundary they must not
cross, not a 64K boundary. We are merely limited to a 64K maximum
segment size. Therefore, the DMA scatter/gather table fill code can be
greatly simplified, and we need not cut in half the S/G table size as
reported to the SCSI layer.
Also, the driver forget to turn on 64-bit DMA at the PCI layer. All
other data structures (both hardware and software) have been prepped for
64-bit PCI DMA. It was simply never turned on. <fingers crossed> let's
see if it still works...
Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions