From: Doron Holan [MSFT] on 28 Apr 2010 15:33 start adding logging to your driver and try to root cause it. changing how the device enumerates is a band aid, not the real fix (and as tim pointed out, there is no way to do what you want to do here, there is nothing for you to filter) d -- This posting is provided "AS IS" with no warranties, and confers no rights. "Abei" <Abei(a)discussions.microsoft.com> wrote in message news:725E07C8-8A4C-4B78-B079-C77040D47F10(a)microsoft.com... > Hi, Tim! > Our device driver can pass Windows 7/vista/XP x86 & x64 all device DTM > test > items and get log already. > But it failed on system DTM test for a type of netbook. > We can't know where is wrong of our driver. > > -- > Abei > > > "Tim Roberts" wrote: > >> Abei <Abei(a)discussions.microsoft.com> wrote: >> > >> >Yes, I want the host controller to enumerate my device as a compsite >> >device. >> >My device reports it as a single function device. It will cause S3/S4 >> >resume >> >system failed. But if I modify the device descriptor to a compsite >> >device, it >> >can't duplicate this issue. >> >> That is a driver issue, not a hardware issue. When you make it >> composite, >> all you are doing is adding another driver to the stack. Anything it can >> do, you can do in YOUR driver. What class of device is this? >> >> >Since device descriptor (firmed in chip) can't be changed, I want to >> >modify >> >it in a lower filter driver before host controller driver gets my devcie >> >descriptor. Can this lower filter driver achieve this goal? >> >> No. The host controller driver is the bottom-most driver in the USB >> stack. >> It performs transfers through DMA. It doesn't send any requests down for >> you to filter, because there IS no driver below it. >> -- >> Tim Roberts, timr(a)probo.com >> Providenza & Boekelheide, Inc. >> . >>
First
|
Prev
|
Pages: 1 2 Prev: Windows7 64bit 1394 isochronous attach buffers fails Next: _ACPI_CMOS_INTERFACE_STANDARD |