src-test2/sys/dev/mly, branch release/5.3.0_cvs

This commit was manufactured by cvs2svn to create tag

2004-11-04T19:12:42Z

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

Do the dreaded s/dev_t/struct cdev */

2004-06-16T09:47:26Z

Bump __FreeBSD_version accordingly.

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

Device megapatch 4/6:

2004-02-21T21:10:55Z

Introduce d_version field in struct cdevsw, this must always be initialized to D_VERSION. Flip sense of D_NOGIANT flag to D_NEEDGIANT, this involves removing four D_NOGIANT flags and adding 145 D_NEEDGIANT flags.

Device megapatch 1/6:

2004-02-21T19:42:58Z

Free approx 86 major numbers with a mostly automatically generated patch. A number of strategic drivers have been left behind by caution, and a few because they still (ab)use their major number.

Fixed a memory leak.

2004-01-18T12:49:36Z

Reported by: Stanford Metacompilation research group

Use PCIR_BAR(x) instead of PCIR_MAPS.

2003-09-02T17:30:40Z

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

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

2003-08-22T06:42:59Z

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

Don't provide mutexes for static busdma allocations.

2003-08-11T03:39:41Z

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