src/sys/dev/ubsec, branch release/5.3.0_cvs

This commit was manufactured by cvs2svn to create tag

2004-11-04T19:12:42+00:00

'RELENG_5_3_0_RELEASE'.

This commit was manufactured to restore the state of the 5.3-RELEASE image.

Add missing includes

2004-05-30T20:08:47+00:00

Convert callers to the new bus_alloc_resource_any(9) API.

2004-03-17T17:50:55+00:00

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

Use __FBSDID().

2003-08-24T17:55:58+00:00

Also some minor style cleanups.

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

2003-08-22T07:08:17+00:00

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:11+00:00

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:06+00:00

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

Add support to eliminate a context switch per crypto op when using the

2003-06-27T20:07:10+00:00

software crypto device:

o record crypto device capabilities in each session id
o add a capability that indicates if the crypto driver operates synchronously
o tag the software crypto driver as operating synchronously

This commit also introduces crypto session id macros that cleanup their
construction and querying.

Redo locking for proper SMP operation:

2003-06-02T23:32:03+00:00

o replace driver-global lock with three locks: one for the handling of mcr1
  operations, one for handling of mcr2 operations, and one for the mcr1
  free list
o mark the interrupt handler MPSAFE
o don't use locking on detach; disabling interrupts is sufficient (I think)

recognize the Sun Crypto 5821 and Crypto 1K cards;

2003-04-27T04:26:22+00:00

they both use the Broadcom 5821

Submitted by:	Panagiotis Astithas
MFC after:	1 day