Re: Driver Load Sequence
- From: "EZ" <EZ@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 26 May 2005 15:18:02 -0700
Hi Bruce,
Thanks for your respond. Yes i have changed the load order in platform.reg
for OHCI as well as USBFN dlls to be higher than all the other modules.
This changed the order of loading relative to some other modules but it
didn't do exactly what i wanted to do which was load the OHCI.dll at the very
end.
Is it correct to assume that the "order" entry in the platform.reg is
somehow only advisory? There are some other USB related modules which might
be creating dependencies for example the USBD.dll. If this is the case i will
need to go and change the load order for these ones as well.
EZ
"Bruce Eitman (eMVP)" wrote:
> Have you tried changing the order of the USB Host driver so that it loads
> last?
>
> --
> 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
>
>
> "EZ" <EZ@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:FD74D2DD-C9C6-488F-A432-BF006048FA41@xxxxxxxxxxxxxxxx
> > Thanks Steve. The problem is that detaching the external device from the
> USB
> > port doesn't un-load the driver, the driver gets stuck in somehow as if
> the
> > OS doesnot know that it is there. But this only happens if WinCE is
> started
> > with the USB device attached to the USB port otherwise everything works
> fine.
> > When the WinCE device is booted with the external FTDI device physically
> > attached to the USB, the Host driver loads the FTDI_SER.DLL at boot time.
> The
> > problem is that under this senario the Host Controller can not un-load the
> > driver when the external device is detached. In a way the OHCI driver gets
> > stuck and it wouldn't work properly either. Basically the WinCE device can
> > only handle the external USB device properly if it is attached after
> > completion of the boot up sequence.
> > So to resolve this problem i need to tell WinCE not to load the FTDI
> driver
> > until every other DLL is loaded and boot up sequence is complete.
> > Alternatively if it is not possible to tell wince to load the driver until
> > after system boot, i need to somehow un-load the ftdi driver as soon as it
> > gets loaded during the system boot up and let the boot up sequence finish
> and
> > then load the ftdi driver. Maybe i could write a script that runs at start
> > up, but by what i read from your post doesnt look like that can be doen
> > programatically, something using insmod and rmmod in unix like OSs.
> >
> > Regards,
> > EZ.
> >
> > "Steve Maillet (eMVP)" wrote:
> >
> > > You can't programmatically load/unload USB client drivers only the USB
> host
> > > driver can do that. Just unplug the device and the host driver will
> unload
> > > the client driver.
> > >
> > > --
> > > Steve Maillet
> > > EmbeddedFusion
> > > www.EmbeddedFusion.com
> > > smaillet at EmbeddedFusion dot com
> > >
> > >
> > >
>
>
>
.
- Follow-Ups:
- Re: Driver Load Sequence
- From: Steve Maillet \(eMVP\)
- Re: Driver Load Sequence
- References:
- Driver Load Sequence
- From: EZ
- Re: Driver Load Sequence
- From: Steve Maillet \(eMVP\)
- Re: Driver Load Sequence
- From: EZ
- Re: Driver Load Sequence
- From: Bruce Eitman \(eMVP\)
- Driver Load Sequence
- Prev by Date: CE debugging very slow with HyperThread host
- Next by Date: Re: Driver Load Sequence
- Previous by thread: Re: Driver Load Sequence
- Next by thread: Re: Driver Load Sequence
- Index(es):
Relevant Pages
|
