From bf4a98bc2d6bb27eb631548362c12e0df3df17cb Mon Sep 17 00:00:00 2001 From: Rolf Eike Beer Date: Fri, 14 Jul 2006 00:24:24 -0700 Subject: [PATCH] --- yaml --- r: 32648 b: refs/heads/master c: b9432e4d8866606466117664472c58ac981ea4f4 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/DMA-mapping.txt | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/[refs] b/[refs] index b16f1fc2a2d7..3b7c3cccdc8e 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: d247e2c661f28a21e5f9a8d672e1e88a7c1c5d4a +refs/heads/master: b9432e4d8866606466117664472c58ac981ea4f4 diff --git a/trunk/Documentation/DMA-mapping.txt b/trunk/Documentation/DMA-mapping.txt index 7c717699032c..63392c9132b4 100644 --- a/trunk/Documentation/DMA-mapping.txt +++ b/trunk/Documentation/DMA-mapping.txt @@ -698,12 +698,12 @@ these interfaces. Remember that, as defined, consistent mappings are always going to be SAC addressable. The first thing your driver needs to do is query the PCI platform -layer with your devices DAC addressing capabilities: +layer if it is capable of handling your devices DAC addressing +capabilities: - int pci_dac_set_dma_mask(struct pci_dev *pdev, u64 mask); + int pci_dac_dma_supported(struct pci_dev *hwdev, u64 mask); -This routine behaves identically to pci_set_dma_mask. You may not -use the following interfaces if this routine fails. +You may not use the following interfaces if this routine fails. Next, DMA addresses using this API are kept track of using the dma64_addr_t type. It is guaranteed to be big enough to hold any