src-test2/sys/dev/sym, branch release/5.4.0_cvs

This commit was manufactured by cvs2svn to create tag

2005-05-07T17:51:10Z

'RELENG_5_4_0_RELEASE'. This commit was manufactured to restore the state of the 5.4-RELEASE image.

MFC: /- and my license changes for sys/[a-d]

2005-01-30T01:00:13Z

MFC: Make module depend on cam && pci.

2004-09-19T01:07:23Z

Approved by: re

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

unifdef old interface support out to prevent false positives.

2003-12-07T05:17:13Z

Suggested by: jeffr, obrien, and others

Use PCIR_BAR(x) instead of PCIR_MAPS.

2003-09-02T17:30:40Z

Glanced over by: imp, gibbs Tested by: i386 LINT

Use __FBSDID().

2003-08-24T18:17:24Z

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.

Remove extraneous semicolons. They are already provided by

2003-08-05T07:22:12Z

the macro definition, and cause the generation of syntactically incorrect code that gcc happens to accept. Reviewed by: schweikh (mentor) MFC after: 4 weeks

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