HP Brio ba200 hp desktop pcs, plug and play for Microsoft Windows 2000 (Micros - Page 13

Play Manager and are exclusively user-mode APIs. The Windows Setup program

Get HP Brio ba200 PDF manuals and user guides View all HP Brio ba200 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 13 highlights

A bus driver performs certain operations on behalf of the devices on its bus but usually does not handle reads and writes to the devices on its bus. (A device's function driver handles reads and writes to a device.) A bus driver acts as a function driver for its controller, adapter, bridge, or other device. Microsoft provides bus drivers for most common buses, including PCI, Plug and Play ISA, SCSI, and USB. Other bus drivers can be provided by IHVs or OEMs. A bus driver can be implemented as a driver/minidriver pair, the way a SCSI port/miniport pair drives a SCSI host adapter. In such driver pairs, one driver is linked to the second driver, and the second driver is a DLL. The ACPI driver fulfills the role of both bus driver and function driver. ACPI allows the system to learn about devices that either do not have a standard way to enumerate themselves (that is, legacy devices) or are newly defined ACPI devices to be enumerated by ACPI (such as the LID device or the embedded controller device). ACPI also installs upper-level filter drivers for devices that have functionality beyond the standard for their bus. For example, if a PCI bus driver installs a graphics controller with power controls that are not supported by the PCI bus, the device can access its added functionality if the ACPI driver loads an upperlevel filter driver for it. X9HÃ9r‰vprÃ9…v‰r…† WDM device drivers are usually the function driver/minidriver pair and filter drivers discussed in the WDM Interface for Plug and Play section above. In addition to providing the operational interface for its device, function drivers play an important role in a power-managed system, contributing information as the policy owner for the device about power management capabilities and carrying out actions related to transitions between sleeping and fully on power states. V†r…H‚qrÃQyˆtÃhqÃQyh’Ã8‚€ƒ‚r‡† The Windows 2000 user-mode APIs for controlling and configuring devices in a Plug and Play environment are 32-bit extended versions of Windows 95-based Configuration Manager APIs. In Windows 95, the Configuration Manager is a virtual device driver (VxD) that exposes these routines as services to both ring 0 and ring 3 components. In Windows 2000, these routines expose functionality from the user-mode Plug and Play Manager and are exclusively user-mode APIs. The Windows Setup program installs the drivers, and so on. The 32-bit device installer installation APIs that Setup uses to install drivers are functionally a superset of the Windows 95 SetupxDi routines. Windows 2000 provides APIs that applications can use for customized hardware event management and to create new hardware events. Windows 2000 White Paper 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
Windows 2000 White Paper
9
A bus driver performs certain operations on behalf of the devices on its bus but
usually does not handle reads and writes to the devices on its bus. (A device’s
function driver handles reads and writes to a device.) A bus driver acts as a function
driver for its controller, adapter, bridge, or other device.
Microsoft provides bus drivers for most common buses, including PCI, Plug and
Play ISA, SCSI, and USB. Other bus drivers can be provided by IHVs or OEMs. A
bus driver can be implemented as a driver/minidriver pair, the way a SCSI
port/miniport pair drives a SCSI host adapter. In such driver pairs, one driver is
linked to the second driver, and the second driver is a DLL.
The ACPI driver fulfills the role of both bus driver and function driver. ACPI allows
the system to learn about devices that either do not have a standard way to
enumerate themselves (that is, legacy devices) or are newly defined ACPI devices
to be enumerated by ACPI (such as the LID device or the embedded controller
device). ACPI also installs upper-level filter drivers for devices that have
functionality beyond the standard for their bus. For example, if a PCI bus driver
installs a graphics controller with power controls that are not supported by the PCI
bus, the device can access its added functionality if the ACPI driver loads an upper-
level filter driver for it.
WDM device drivers are usually the function driver/minidriver pair and filter drivers
discussed in the WDM Interface for Plug and Play section above. In addition to
providing the operational interface for its device, function drivers play an important
role in a power-managed system, contributing information as the policy owner for
the device about power management capabilities and carrying out actions related to
transitions between sleeping and fully on power states.
The Windows 2000 user-mode APIs for controlling and configuring devices in a
Plug and Play environment are 32-bit extended versions of Windows 95–based
Configuration Manager APIs. In Windows 95, the Configuration Manager is a virtual
device driver (VxD) that exposes these routines as services to both ring 0 and ring 3
components.
In Windows 2000, these routines expose functionality from the user-mode Plug and
Play Manager and are exclusively user-mode APIs. The Windows Setup program
installs the drivers, and so on. The 32-bit device installer installation APIs that Setup
uses to install drivers are functionally a superset of the Windows 95 SetupxDi
routines.
Windows 2000 provides APIs that applications can use for customized hardware
event management and to create new hardware events.