designed exclusively to be used with a particular class of devices. Such Wire Adapters must not have any ports that are user accessible.

If the number of blocks per RPipe is dynamically manageable by host software then a value of “zero” must be reported in the wBlocks field of an RPipe Descriptor after reset. In this case, Host software is responsible to correctly assign the amount of buffer per RPipe. The total number of available buffer blocks is determined by the wRPipeMaxBlock field in the Wire Adapter Descriptor. This implementation choice is suitable for an allpurpose Wire Adapter.

8.2Descriptors

Wire Adapter descriptors are derived from the general USB device framework. Wire Adapter descriptors define a Wire Adapter device. The host accesses these descriptors through the Wire Adapter’s control endpoint. The Wire Adapter class pre-defines certain fields in standard USB descriptors. Other fields are either implementation-dependent or not applicable to this class.

The Wire Adapter class defines additional device class descriptors. Vendor-specific descriptors may be defined. Host Wire Adapter descriptors are described in Section 8.5.2. Device Wire Adapter descriptors are described in Section 8.4.3.

8.3Requests

All Wire Adapter devices must implement all required standard commands in the core device framework. All Wire Adapters must support the Class specific requests in Section 8.3.1.

Host Wire Adapter specific requests are specified in Section 8.5.3.

Device Wire Adapters must support all required Wireless USB extensions to the Chapter 9 framework as specified in the Wireless USB framework chapter. A DWA must support the class specific requests defined in Section 8.4.4.

The valid values for the bmRequestType.Recipient field are extended in this class specification to allow addressing of Ports and RPipes as illustrated in Table 8-3.

Table 8-3. Recipient Encoding Extension

205