Re: driver loading sequence
- From: "Bruce Eitman [eMVP]" <beitman.nospam@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 29 Dec 2006 11:58:01 -0500
That all depends on the requiements of these drivers. I suspect that a
chapter or two could be written in a book on this topic. There are lots of
tools available, including merge them into one driver. But without knowing
anything about what you are doing, it is impossible to advise you.
--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net
Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member
<suqian99@xxxxxxxxxxx> wrote in message
news:1167405739.480547.52570@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have driver A,B and C. A depends on B and B depends on C. So
obviously I will load C first and then B and then A. When C is ready,
it will set an event using SetEvent function to tell B, so does B. B
will wait C's event in init to finish its initialization. So does A.
But I found that waiting an event calling WaitforSingleOject isn't a
good idea in the init function. this will slow down the whole system's
booting up.
any good approach to this issue?
thanks,
Mike
.
- Follow-Ups:
- Re: driver loading sequence
- From: Steve Maillet \(eMVP\)
- Re: driver loading sequence
- References:
- driver loading sequence
- From: suqian99
- driver loading sequence
- Prev by Date: Re: Excel and Powerpoint Viewer in WinCE 5.0
- Next by Date: Re: about samsung smdk2440 sd driver questions
- Previous by thread: driver loading sequence
- Next by thread: Re: driver loading sequence
- Index(es):
Relevant Pages
|
|