Re: Starting a driver within a driver...
- From: "Eliyas Yakub [MSFT]" <eliyasy@xxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 18 Jun 2006 04:03:15 GMT
Device #2 depends on Device #1.
Can I do something with dependencies to ensure the OS starts device #1
first, then device #2?
There is no system provided way to control start order of two devices.
Assuming that cannot be done with dependencies, I
need #1 to signal #2 to start--and #2 to start only if #1 is already
started. Then the order in which the OS tells the drivers to start won't
matter--while the dependency effectively holds.
You can devise your own signalling technique. I have used callback objects
(ExCreateCallback) in my drivers to control load order dependencies of two
independent drivers. If you need sample code, send me an email note.
The way I see you solving the problem is that if #2 is started before #1
then #2 would complete the start-irp with STATUS_SUCCESS, but wouldn't
really initialize the device until #1 starts and signals #2. Correct? I'm
not sure all the thing that PCI bus driver does when it receives the
start-irp, but wouldn't you have any problem if start-device of #2 is
handled by the pci bus before #1?
.
- Follow-Ups:
- Re: Starting a driver within a driver...
- From: Ray Trent
- Re: Starting a driver within a driver...
- References:
- Starting a driver within a driver...
- From: Cosmo
- Starting a driver within a driver...
- Prev by Date: Re: IOCTL_READ_REGISTERS
- Next by Date: Re: IRQ assignment in Windows 2K/XP/2003...
- Previous by thread: Starting a driver within a driver...
- Next by thread: Re: Starting a driver within a driver...
- Index(es):
Relevant Pages
|