src-test2/sys/dev/ubsec, branch release/6.2.0_cvs

This commit was manufactured by cvs2svn to create tag

2007-01-11T22:54:46Z

'RELENG_6_2_0_RELEASE'. This commit was manufactured to restore the state of the 6.2-RELEASE image.

MFC: Synchronize crypto drivers with the code from the HEAD branch.

2006-09-04T15:18:50Z

Use BUS_PROBE_DEFAULT in preference to 0. Also for vx, return

2005-03-01T07:50:12Z

BUS_PROBE_LOW_PRIORITY in stead of ifdef for devices that xl and vx both support so that xl will snarf them on up.

Start each of the license/copyright comments with /*-, minor shuffle of lines

2005-01-06T01:43:34Z

Add missing includes

2004-05-30T20:08:47Z

Convert callers to the new bus_alloc_resource_any(9) API.

2004-03-17T17:50:55Z

Submitted by: Mark Santcroos Reviewed by: imp, dfr, bde

Use __FBSDID().

2003-08-24T17:55:58Z

Also some minor style cleanups.

Prefer new location of pci include files (which have only been in the

2003-08-22T07:08:17Z

tree for two or more years now), except in a few places where there's code to be compatible with older versions of FreeBSD.

Change instances of callout_init that specify MPSAFE behaviour to

2003-08-19T17:51:11Z

use CALLOUT_MPSAFE instead of "1" for the second parameter. This does not change the behaviour; it just makes the intent more clear.

Mega busdma API commit.

2003-07-01T15:52:06Z

Add two new arguments to bus_dma_tag_create(): lockfunc and lockfuncarg. Lockfunc allows a driver to provide a function for managing its locking semantics while using busdma. At the moment, this is used for the asynchronous busdma_swi and callback mechanism. Two lockfunc implementations are provided: busdma_lock_mutex() performs standard mutex operations on the mutex that is specified from lockfuncarg. dftl_lock() is a panic implementation and is defaulted to when NULL, NULL are passed to bus_dma_tag_create(). The only time that NULL, NULL should ever be used is when the driver ensures that bus_dmamap_load() will not be deferred. Drivers that do not provide their own locking can pass busdma_lock_mutex,&Giant args in order to preserve the former behaviour. sparc64 and powerpc do not provide real busdma_swi functions, so this is largely a noop on those platforms. The busdma_swi on is64 is not properly locked yet, so warnings will be emitted on this platform when busdma callback deferrals happen. If anyone gets panics or warnings from dflt_lock() being called, please let me know right away. Reviewed by: tmm, gibbs