A reference for Designing Servers and Peripherals for the Microsoft® Windows® 2000 Server Family of Operating Systems Intel Corporation and Microsoft Corporation Publication Date—June 30, 2000
Download 1.64 Mb.
|
- Navigate this page:
- 57. All USB hardware complies with USB 1.1
- 58. USB devices and drivers support maximum flexibility of hardware interface options
- 59. System and devices comply with USB power management requirements
- 60. USB devices comply with their related USB device class specifications
- 61. USB hubs are self-powered
- 62. USB devices install without pre-loading software
- 63. Any subsystems implementing I 2 O comply with standards and other requirements
- 64. System does not include ISA or LPC expansion slots
- 65. System does not include embedded ISA or LPC network adapters, storage controllers, or graphics adapters
- 67. System that supports Winsock Direct connectivity meets requirements for device and driver support
USB RequirementsThis section summarizes requirements for Universal Serial Bus. 56. System includes USB controller with at least one USB portRequired To facilitate the eventual migration away from legacy connections for keyboards, pointing devices, serial devices, and parallel devices, server designers must integrate USB functionality into their server platforms with the minimum support being one USB controller with at least one available USB port. USB ports must comply with the related USB requirements in this guide. 57. All USB hardware complies with USB 1.1Required All USB hardware present on a server system and USB devices, including hubs, must comply with USB 1.1 or later. When a system has more than one host controller, each host controller must provide full bandwidth and isochronous support. Host controllers should be located on PCI to meet this requirement. The host controller providing USB 1.1 functionality must comply with the specifications for either Open Host Controller Interface (OpenHCI), published by Compaq, Microsoft, and National Semiconductor, or Universal HCI (UHCI), published by Intel. Hardware manufacturers who design to one of these specifications are not required to provide an additional Windows 2000 device driver for their host controller. Multiple OpenHCI and UHCI USB controllers are supported concurrently by the operating system. 58. USB devices and drivers support maximum flexibility of hardware interface optionsRequired Device and driver designs must provide maximum flexibility for interface options to allow user-preference coordination by the operating system or other resource managers. This flexibility allows graceful use of multiple simultaneous devices and applications in a dynamic environment. Minimum requirements consist of the following:
59. System and devices comply with USB power management requirementsRequired The server system must comply with the power management requirements in USB 1.1 or later. In addition, USB devices must comply with the Interface Power Management feature in the USB Common Class Specification, Revision 1.1 or later. 60. USB devices comply with their related USB device class specificationsRequired A USB peripheral that fits into one of the USB device class definitions must comply with the related USB device class specification. USB class drivers in the operating system are implemented to support compliant devices in each particular class. Class driver extensions and WDM allow hardware manufacturers to innovate and differentiate their products while still complying with class specifications in their base operational modes. 61. USB hubs are self-poweredRequired This requirement does not apply for hubs integrated into keyboards. To minimize USB power consumption requirements, bus-powered hubs must provide ports that can be individually power switched. This contributes to the goal of reducing overall system power consumption. 62. USB devices install without pre-loading softwareRequired A user must not be required to install software before hot-plugging a USB device. Instead, the user must be able to hot-plug the USB device, and then load any software in response to the operating system detection of the newly-attached device. Other Bus RequirementsThis section summarizes requirements related to other buses. 63. Any subsystems implementing I2O comply with standards and other requirementsRequired If I2O is implemented in a system, it must meet the requirements defined in this guide and in the I2O Architecture Specification, Version 1.5 or later, available at http://www.i2osig.org. If I2O is implemented on a system, the system firmware must support I2O devices for the following configurations:
64. System does not include ISA or LPC expansion slotsRequired No ISA or LPC expansion slots are allowed in servers designed to comply with these guidelines. The benefits of an ISA-free system include improved performance, easier and more stable system configuration, and lower support costs. There are no permitted exemption cases. 65. System does not include embedded ISA or LPC network adapters, storage controllers, or graphics adaptersRequired The benefits of an ISA-free system include improved performance, easier and more stable system configuration, and lower support costs. 66. System does not include ISA or LPC expansion devicesRequired An ISA or LPC expansion device in this context is defined as being an expansion adapter or device installed in an ISA or LPC slot. No ISA or LPC expansion devices are allowed. There are no permitted exemptions to this requirement.
Systems are not required to provide Winsock Direct (WSD) connectivity capabilities. However, those systems that do must meet the following guidelines:
The Winsock Direct Specification is provided in the Windows 2000 DDK, and is available online at http://www.microsoft.com/DDK/DDKdocs/Win2k/wsdpspec_1h66.htm.
Hardware characteristics and provider guidelines are defined in the Windows 2000 DDK, and are available online at http://www.microsoft.com/DDK/DDKdocs/Win2k/wsd_hw_0aur.htm. Additionally, hardware must have page tables to translate user addresses to physical addresses. This allows direct user-mode access to the hardware, permitting endpoint resources to be mapped directly into the address space of a user-mode process. This permits application processes to post messaging requests directly to the hardware, with no system calls and no intermediate data copying. Notes: 1. Winsock Direct and associated hardware are targeted for use in physically secure computer systems and environments, such as those associated with “back end” or “glass house” computing environments. 2. Vendors who are sizing their page table hardware should take into account the number of simultaneous connections expected to be supported by the hardware in conjunction with the applications using this connection. The number of simultaneous connections may range widely (from thousands to hundreds). In addition to the number of simultaneous connections, designers need to take into account the page size (specific to the host computer system) and whether the connection is registering memory for RDMA operations in addition to memory registered for messages. Cards that support thousands of simultaneous connections will need to map tens of thousands of page table entries.
Directory: download download -> Performance Tuning Guidelines for Windows Server 2008 May 20, 2009 Abstract download -> Northern England’s set-jetting locations download -> Bbc archives: Beyond the programme download download -> Occupational health and safety download -> Dynatest 3031 lwd light Weight Deflectometer download -> Forth coming competitive exams download -> English Olympiad Tasks: 10 th form Аудіювання, 10 клас. Текст download -> Brush High School Morning Announcements Friday, September 05, 2014 all school download -> Year 9 The Arts — Music download -> Years 7 and 8 standard elaborations — Australian Curriculum: Music draft Download 1.64 Mb. Share with your friends:
|