Searched refs:unmap (Results 1 – 11 of 11) sorted by relevance
/linux-2.4.37.9/Documentation/ |
D | DMA-mapping.txt | 307 To unmap and free such a DMA region, you call: 419 packets, map/unmap them with the PCI_DMA_TODEVICE direction 420 specifier. For receive packets, just the opposite, map/unmap them 426 context. There are two versions of each map/unmap, one which will 427 map/unmap a single memory region, and one which will map/unmap a 439 and to unmap it: 448 map/unmap interface pair akin to pci_{map,unmap}_single. These 490 To unmap a scatterlist, just call: 519 After the last DMA transfer call one of the DMA unmap routines 664 argument is the same as for pci_{map,unmap}_single(). The same rules [all …]
|
D | IO-mapping.txt | 164 /* unmap when we unload the driver */
|
/linux-2.4.37.9/Documentation/sparc/ |
D | sbus_drivers.txt | 73 unload or similar) you must unmap them. You must treat them as 75 (unmap) when you are done with it. 114 And here is how you might unmap these registers later at
|
/linux-2.4.37.9/Documentation/video4linux/bttv/ |
D | PROBLEMS | 46 That's because XFree and some AcceleratedX versions do not send unmap
|
/linux-2.4.37.9/Documentation/arm/SA1100/ |
D | DMA | 66 functions are pci_alloc_consistent(), pci_map_single() and their unmap 225 /* unmap the DMA buffer (actually doing cache coherency on ARM) */
|
/linux-2.4.37.9/Documentation/vm/ |
D | locking | 96 from disk, and an unmap -> swap_free making the handle unused, the swap
|
/linux-2.4.37.9/drivers/atm/ |
D | fore200e.h | 822 void (*unmap)(struct fore200e*); member
|
D | fore200e.c | 428 fore200e->bus->unmap(fore200e); in fore200e_shutdown()
|
/linux-2.4.37.9/Documentation/networking/ |
D | 8139too.txt | 370 * Correct potential oops bug in PCI DMA unmap code
|
/linux-2.4.37.9/drivers/scsi/ |
D | ChangeLog.sym53c8xx | 149 - Revert the change in 'ncr_flush_done_cmds()' but unmap the
|
/linux-2.4.37.9/arch/sparc/kernel/ |
D | entry.S | 982 bcs,a 2f ! no, unmap one.
|