X-Git-Url: http://git.onelab.eu/?a=blobdiff_plain;f=Documentation%2FDMA-mapping.txt;h=7c717699032c90f403432ef793cfeed8c359fe7b;hb=9464c7cf61b9433057924c36e6e02f303a00e768;hp=63392c9132b4d08bf32f3fab82cc0c14c39e15b1;hpb=41689045f6a3cbe0550e1d34e9cc20d2e8c432ba;p=linux-2.6.git

diff --git a/Documentation/DMA-mapping.txt b/Documentation/DMA-mapping.txt
index 63392c913..7c7176990 100644
--- a/Documentation/DMA-mapping.txt
+++ b/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 if it is capable of handling your devices DAC addressing
-capabilities:
+layer with your devices DAC addressing capabilities:
 
-	int pci_dac_dma_supported(struct pci_dev *hwdev, u64 mask);
+	int pci_dac_set_dma_mask(struct pci_dev *pdev, u64 mask);
 
-You may not use the following interfaces if this routine fails.
+This routine behaves identically to pci_set_dma_mask.  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