Plug And Play Free Online

  1. Plug And Play Free Game
  2. Plug And Play Weird Game
  3. Plug And Play The Game
-->

We connect the largest corporations to the world's best startups through industry-focused accelerator programs in Silicon Valley and beyond. Plug and Play is a free smart home APP that allows you to remote control smart switch, smart power strip devices of different brands. It supports voice controlling the devices with Amazon Alexa, the Google Assistant and TmallGenie.

This section describes the enumeration process on the Universal Serial Bus.

Plug and play free online

When a device is plugged in to a Windows-based computer, the Windows USB stack enumerates the device, extracting details from the device including the interface descriptor (or descriptors) of the device, and then generates a set of hardware IDs and compatible IDs for the device.

For a complete list of USB hardware IDs, see the 'Device Identification Strings' section under Device Installation.

The examples in the following sections illustrate two scenarios:

  • USB IDs for a single interface USB device
  • USB IDs for a multi-interface (composite) USB device

Example 1: Single Interface HID USB Device

This example shows how the hardware IDs and compatible IDs are generated for a single-interface USB device on a system running Windows 2000 or Windows XP.

When the device is originally enumerated by the USB stack, the USBHUB driver extracts idVendor, idProduct, and bcdDevice from the device descriptor. These three fields are incorporated to generate a USB hardware ID. Note that the vendor, device, and revision numbers are always stored in hexadecimal format.

The generation of the compatible ID for the device is more complicated. The class code, subclass code, and protocol code are determined by the interface descriptor's bInterfaceClass, bInterfaceSubClass, and bInterfaceProtocol. These values are in two-digit hexadecimal format.

Note If you are providing an INF, your hardware identifiers should match the bold identifiers in the left column of the following table. (You should avoid using the compatible identifiers listed in the right column.)

Hardware Identifiers: Compatible Identifiers

USBVid_xxxx&Pid_yyyy&Rev_zzzz: USBClass_aa&SubClass_bb&Prot_cc

USBVid_xxxx&Pid_yyyy: USBClass_aa&SubClass_bb

Plug And Play Free Game

****: USBClass_aa

Example 2: Multiple Interface/Function HID USB Device (Composite Device)

Plug And Play Weird Game

USB devices with multiple functions are called composite devices. This example shows how the hardware IDs and compatible IDs are generated for composite USB devices on Windows. When a new USB composite device is plugged into a computer system running Windows, the USBHUB driver creates a physical device object (PDO) and notifies the operating system that its set of child devices has changed. After querying the hub driver for the hardware IDs associated with the new PDO, the system searches the appropriate INF files to find a match for the identifiers. If a vendor chooses to load just one driver for the entire device (that is, not using the composite device driver) and multiplex all interfaces in software with that driver, the vendor should specify a hardware ID match to prevent the operating system from picking up the lower-ranking match (USBCOMPOSITE).

Note If you are providing an INF, your hardware identifiers should match the bold identifiers in the left column of the following table. (You should avoid using the compatible identifiers listed in the right column.)

Hardware Identifiers: Compatible Identifiers

USBVid_xxxx&Pid_yyyy&Rev_zzzz: USBClass_aa&SubClass_bb&Prot_cc

Plug And Play The Game

USBVid_xxxx&Pid_yyyy: USBClass_aa&SubClass_bb

Plug And Play Free Online

****: USBClass_aa

****: USBCOMPOSITE

If, however, no hardware match is found, Windows Plug and Play makes use of the USBCOMPOSITE identifier to load the USB Generic Parent driver (USBCCGP). The Generic Parent driver then creates a separate set of PDOs (one for every interface) with a separate set of hardware IDs for each interface of the composite device. The following section displays the format of hardware IDs for child PDOs.

To build the set of hardware IDs for each interface’s PDO, the USBCCGP driver appends the interface number (which is a zero-based hexadecimal value) to the end of the hardware ID.

The class code, subclass code, and protocol code are determined by the bInterfaceClass, bInterfaceSubClass, and bInterfaceProtocol fields of the interface descriptor, respectively. These values are in two-digit hexadecimal format.

Note If you are providing an INF, either to load your driver or to provide a friendly device name, your hardware identifiers should match the bold identifiers in the left column of the following table. (You should avoid using the compatible identifiers listed in the right column.)

Hardware Identifiers: Compatible Identifiers

USBVid_xxxx&Pid_yyyy&Rev_zzzz&MI_ww: USBClass_aa&SubClass_bb&Prot_cc

USBVid_xxxx&Pid_yyyy&MI_ww: USBClass_aa&SubClass_bb

****: USBClass_aa

-->

Plug and Play (PnP) is a combination of hardware and software support that enables a computer system to recognize and adapt to hardware configuration changes with little or no intervention by a user. A user can add devices to, and remove devices from, a computer system without having to do awkward and confusing manual configuration, and without having knowledge of intricate computer hardware. For example, a user can dock a portable computer and use the docking station keyboard, mouse, and monitor without making manual configuration changes.

PnP requires support from device hardware, system software, and drivers. Initiatives in the hardware industry define standards (such as the PnP ISA definition and the PC Card standard) for easy identification of add-in boards and basic system components. This Windows Driver Kit (WDK) documentation focuses on the system software support for PnP and how drivers use that support to implement PnP.

The system software support for PnP, together with PnP drivers provides the following:

  • Automatic and dynamic recognition of installed hardware

    The system software recognizes hardware during initial system installation, recognizes PnP hardware changes that occur between system boots, and responds to run-time hardware events such as docking or undocking and device insertion or removal.

  • Hardware resource allocation (and reallocation)

    The PnP manager determines the hardware resources requested by each device (for example, input/output ports [I/O], interrupt requests [IRQs], direct memory access [DMA] channels, and memory locations) and assigns hardware resources appropriately. The PnP manager reconfigures resource assignments when necessary, such as when a new device is added to the system that requires resources already in use.

    Drivers for PnP devices do not assign resources; instead, the requested resources for a device are identified when the device is enumerated. The PnP manager retrieves the requirements for each device during resource allocation. Resources are not dynamically configurable for legacy devices, so the PnP manager assigns resources to legacy devices first.

  • Loading of appropriate drivers

    The PnP manager determines which drivers are required to support each device and loads those drivers.

  • A programming interface for drivers to interact with the PnP system

    The interface includes I/O manager routines, Plug and Play minor IRPs, required standard driver routines, and information in the registry.

  • Mechanisms for drivers and applications to learn of changes in the hardware environment and take appropriate actions

    PnP enables drivers and user-mode code to register for, and be notified of, certain hardware events.

PnP drivers are an important part of PnP support. For a driver to qualify as PnP it must provide the required PnP entry points, handle the required PnP IRPs, and follow PnP guidelines.

This section contains the following additional topics: