ouyang kai wrote:
>
> Part 1.1.1 Type: Plain Text (text/plain)
> Encoding: quoted-printable
>
> Name: kernel_init_problem.txt
> kernel_init_problem.txt Type: Plain Text (text/plain)
> Encoding: quoted-printable
If you are talking about the fxp driver, then you need to look
in /usr/src/sys/dev/fxp/if_fxp.c, around line 240:
DRIVER_MODULE(if_fxp, pci, fxp_driver, fxp_devclass, 0, 0);
DRIVER_MODULE(if_fxp, cardbus, fxp_driver, fxp_devclass, 0, 0);
DRIVER_MODULE(miibus, fxp, miibus_driver, miibus_devclass, 0, 0);
The definition of DRIVER_MODULE is variant, based on whether
the code is a loadable module, or is compiled into the kernel.
The original intent of the SYSINIT code was to erase the
distinction between code statically linked into the kernel,
and code loaded later, as a loadable module.
Specifically, the DRIVER_MODULE() macro uses the DECLARE_MODULE();
see /usr/src/sys/sys/bus.h, in which it specifies SI_SUB_DRIVERS
as the init_main.c code sort order, and the sub-order within that
as SI_ORDER_MIDDLE.
The DECLARE_MODULE() macro encapsulates a SYSINIT() entry; see
/usr/src/sys/sys/module.h.
The result is that the init_main.c code calls the entry point on
startup to probe the device (see /usr/src/sys/dev/fxp/if_fxp.c).
-- Terry
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
