Re: USBSER.SYS: where to get a bug-free version?

From: Holi (holi_at_nospam.com)
Date: 08/30/04


Date: Mon, 30 Aug 2004 09:40:06 +0200

First of all I'm not so sure if Windows supports composite devices at all - not
to support is one thing, but producing BSOD's because of not supporting is another.

DFU specs (chapt. 4.1.) say:
"During normal run-time operation, the device exposes its normal set of
descriptors. However, the
following additional descriptors are inserted within each run-time
configuration that supports DFU:
- A single DFU class interface descriptor
- A single functional descriptor
4.1.1 Run-Time Device and Configuration Descriptors
The run-time descriptor set exposes the device’s normal run-time device and
configuration descriptors.
The bNumInterfaces field of configuration descriptor of each configuration that
supports DFU is incremented by one to accommodate the addition of the run-time
DFU interface."

Our device was checked by a validator program on MAC OS and looks fine. Windows
ends up with a BSOD with this implementation of DFU specs. I think for DFU
support this IS a requirement.

What do you think?

Holi

Marc Reinig wrote:
> The USB spec has many features. Some are required and are labeled as such.
> Some are optional and are not labeled as required. Which of the required
> features do you feel have been either omitted or incorrectly implemented.
>
> Marc Reinig
> System Solutions



Relevant Pages

  • Re: USBSER.SYS: where to get a bug-free version?
    ... Windows does support composite devices. ... Also, as far as I am aware, Windows does not support DFU as a class and USB ... > following additional descriptors are inserted within each run-time ...
    (microsoft.public.development.device.drivers)
  • Re: USBSER.SYS: where to get a bug-free version?
    ... Windows does support composite devices. ... > Also, as far as I am aware, Windows does not support DFU as a class and USB ... >>and configuration descriptors. ...
    (microsoft.public.development.device.drivers)
  • [PATCH 19/19] iop3xx: IOP 32x and 33x support for the iop-adma driver
    ... Adds the platform device definitions and the architecture specific support ... fix places where software descriptors are assumed to be contiguous, ... iop32x does not support hardware zero sum, ... new file mode 100644 ...
    (Linux-Kernel)
  • Re: Changes in the network interface queueing handoff model
    ... but implemented full queueing support for if_em to ... Actually most em cards support 4096 descriptors each way. ... even the earliest ones supported 4096 descriptors on paper. ... = 256 transmit descriptors on x86 hardware at the time. ...
    (freebsd-arch)
  • Re: Changes in the network interface queueing handoff model
    ... but implemented full queueing support for if_em to ... Actually most em cards support 4096 descriptors each way. ... even the earliest ones supported 4096 descriptors on paper. ... = 256 transmit descriptors on x86 hardware at the time. ...
    (freebsd-net)