Hiten Pandya b77c32a07e Rename BUS_DMAMEM_NOSYNC to BUS_DMA_COHERENT. ... The current name is confusing, because it indicates to the client that a bus_dmamap_sync() operation is not necessary when the flag is specified, which is wrong. The main purpose of this flag is to hint the underlying architecture that DMA memory should be mapped in a coherent way, but the architecture can ignore it. But if the architecture does supports coherent mapping of memory, then it makes bus_dmamap_sync() calls cheap. This flag is the same as the one in NetBSD's Bus DMA. Reviewed by: gibbs, scottl, des (implicitly) Approved by: re@ (jhb)		2003-05-30 20:40:33 +00:00
..
capi	Continue de-counting i4b. Devices i4bctl, i4bcapi, iavc, i4bq921,	2002-09-02 00:52:11 +00:00
driver	Update netisr handling; Each SWI now registers its queue, and all queue	2003-03-04 23:19:55 +00:00
include	add support properly displaying and logging incoming telephone numbers (MSNs)	2002-08-12 07:53:55 +00:00
layer1	Rename BUS_DMAMEM_NOSYNC to BUS_DMA_COHERENT.	2003-05-30 20:40:33 +00:00
layer2	Back out M_* changes, per decision of the TRB.	2003-02-19 05:47:46 +00:00
layer3	Correct typos, mostly s/ a / an / where appropriate. Some whitespace cleanup,	2003-01-01 18:49:04 +00:00
layer4	Gigacommit to improve device-driver source compatibility between	2003-03-03 12:15:54 +00:00