src/sys/dev/hme, branch release/5.2.1

Replace the if_name and if_unit members of struct ifnet with new members

2003-10-31T18:32:15Z

if_xname, if_dname, and if_dunit. if_xname is the name of the interface and if_dname/unit are the driver name and instance. This change paves the way for interface renaming and enhanced pseudo device creation and configuration symantics. Approved By: re (in principle) Reviewed By: njl, imp Tested On: i386, amd64, sparc64 Obtained From: NetBSD (if_xname)

Preparatory commit to allow prototypes in ofw_machdep.h to contain

2003-09-02T20:24:42Z

both newbus types and OFW types. This involves either including or . Reviewed by: jake, jmg, tmm

Use __FBSDID().

2003-08-24T17:55:58Z

Also some minor style cleanups.

s###g

2003-08-23T05:51:03Z

s=include
2003-08-23T00:11:16Z

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

2003-08-22T06:00:27Z

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

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

Some gem and hme hardware bogusly has the intpin register hardwired to

2003-07-01T14:11:04Z

0; detect this case and correct it. While being there, clean up nearby comments.

- Don't call pci_enable_io() in drivers (unless needed for resume).

2003-04-16T03:16:57Z

- Don't test memory/port status and emit an error message; the PCI bus code will do this now.

- Express hard dependencies on bus (pci, isa, pccard) and

2003-04-15T06:37:30Z

network layer (ether). - Don't abuse module names to facilitate ifconfig module loading; such abuse isn't really needed. (And if we do need type information associated with a module then we should make it explicit and not use hacks.)