Re: USBD routines
- From: "Doron Holan [MS]" <doronh@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 3 May 2005 21:34:21 -0700
which routines are you using? there are some routines that are exported via
USBD that are also exposed via a pnp QI.
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ray Trent" <ratrent@xxxxxxxxxxxxx> wrote in message
news:uzHj12AUFHA.2172@xxxxxxxxxxxxxxxxxxxxxxx
> We have a single driver sys file that is loaded for PS/2, Serial, and USB
> devices.
>
> Normally this doesn't cause any problem, but recently we discovered that
> there was one customer that was disabling USB support in their BIOS (I
> don't know how they're dealing with the WHQL requirements). This is
> resulting in usbd.sys not being loaded.
>
> Our driver links to a couple of routines in usbd.sys, so it's
> bluescreening in this configuration (when we're loading for the PS/2
> device).
>
> Normally, I would just do a Needs/Includes to make sure that all drivers
> we depend on are loaded, but I'm having a hard time figuring out what to
> Needs/Includes in this case to make sure usbd.sys is on the system. The
> sections in usb.inf that seem to reference this don't appear to have an
> obvious Needs/Includes path to get to them (i.e. there's no install
> section that actually directly references the CopyFiles section that I can
> find after a brief search).
>
> Does anyone know how to do this? Alternatively are there any better
> suggestions for how to accomplish the same thing?
>
> It's really too bad that there's no kernel equivalent to GetProcAddress,
> because that's really the ideal solution for this kind of situation. I'd
> prefer to not even have usbd.sys loaded in memory if we aren't actually
> adding a USB device object (which would imply that there's a USB port :-).
> This is the case the vast majority of the time.
>
> I mean, I suppose, theoretically, I could create a separate export driver
> that is only installed for USB devices that links to usbd functions and
> then exports them itself via some IOCTL-based equivalent to
> GetProcAddress, but uggghh, what a huge pain/kludge.
>
> BTW, here's one of those pains of kernel development that, as far as I
> know, WDF isn't going to make any easier :-).
> --
> ../ray\..
.
- Follow-Ups:
- Re: USBD routines
- From: Ray Trent
- Re: USBD routines
- References:
- USBD routines
- From: Ray Trent
- USBD routines
- Prev by Date: DriverProc entry point question
- Next by Date: Re: slightly off topic, serial port enumeration problem
- Previous by thread: USBD routines
- Next by thread: Re: USBD routines
- Index(es):
Relevant Pages
|
