macro declares a kernel driver.
expands to the real driver declaration, where the phrase
is used as the naming prefix for the driver and its functions.
Note that it is supplied as plain text, and not a
is the parent bus of the driver (PCI, ISA, PPBUS and others), e.g.
The identifier used in
can be different from the driver name.
Also, the same driver identifier can exist on different busses,
which is a pretty clean way of making front ends for different cards
using the same driver on the same or different busses.
For example, the following is allowed:
DRIVER_MODULE foo isa foo_driver foo_devclass NULL NULL;
DRIVER_MODULE foo pci foo_driver foo_devclass NULL NULL;
is the driver of type
which contains the information about the driver and is therefore one of the
two most important parts of the call to
argument contains the kernel-internal information about the device,
which will be used within the kernel driver module.
argument is the event handler which is called when the driver (or module)
is loaded or unloaded (see
is unused at this time and should be a
macro allows a driver to be registered in a specific order.
This can be useful if a single kernel module contains multiple drivers
that are inter-dependent.
argument should be one of the
initialization ordering constants
The default order for a driver module is
Typically a module will specify an order of
for a single driver to ensure it is registered last.
macro allows a driver to be registered for a specific pass level.
The boot time probe and attach process makes multiple passes over the
Certain critical drivers that provide basic services needed by other
devices are attach during earlier passes.
Most drivers are attached in a final general pass.
A driver that attaches during an early pass must register for a specific
Once a driver is registered it is available to attach to devices for
all subsequent passes.
macro allows a driver to be registered both in a specific order and
for a specific pass level.