usbhosterrors.h File Reference

The device is unsupported- the FDF will not attempt to load drivers for it.

Driver loading has not been enabled.

The configuration descriptor's NumInterfaces is 0.

The configuration descriptor's NumInterfaces does not equal the actual number of (alternate 0) interface descriptors in the configuration bundle.

A Function Driver was not found for at least one interface in the device's selected configuration.

Two of the interfaces in the configuration bundle have the same interface numbers.

A Function Driver has found a problem with the device's descriptors. Such problems include (non-exhaustively) formatting or layout of Class-specific descriptors and alternate interface numbering.

While FDF was busy trying to load FDs the current attached device has been detached by USBDI (physically unplugged or was draining too much current)

During an attachment failure, FDF receives an error from USBDI If the error is not a known expected error then FDF will report it with the following error code -6628, as a KErrUsbAttachmentFailureGeneralError

If a Function Driver or Function Driver upgrade is installed or uninstalled then the FDF receives notification of this from ECom and will update its list of Function Driver Proxies accordingly. This may involve an allocation which therefore may fail however there is no point in the FDF propegating this failure (via a leave) back up the call stack as the originator is ECom. In the event that the FDF does encounter OOM then its list of proxy function drivers will be out of date, this error code indicates such a situation.