A3.1.2 Windows Support for Mobile System Displays
http://www.microsoft.com/hwdev/tech/display/mobiledisplay.asp
Note: This is a general reference, not a requirement.
A3.2 Mobile PC Client - Industry Standards
Note: This list provides complete titles and web locations for references cited. The listing of a reference here does not imply that complete compliance with that reference is a Windows Logo Program requirement.
A3.2.1 DELETED A3.2.2 DELETED A3.2.3 – See B4.2.4.2 A3.3 Mobile PC Client - Quality
See A1.3.
A3.4.1 Power and power management requirements A3.4.1.1 DELETED A3.4.1.2 Mobile system implements either S1 or S3, S4, and S5 sleep states
No "wake from S3 or S4" requirement.
See A1.1.2
A3.4.1.3 DELETED A3.4.1.4 DELETED A3.4.1.5 Systems implementing processor performance states must use native Windows support.
This means that all performance policy and switching must be done by the operating system. See "Windows XP Native Processor Performance Control" at http://www.microsoft.com/hwdev/tech/onnow/.
A3.4.2 BIOS requirements A3.4.2.1 DELETED A3.4.2.2 Support PXE if system includes integrated network adapter. A3.4.3 DELETED A3.4.4 Mobile system contains required devices and buses A3.4.4.1 DELETED A3.4.4.2 DELETED A3.4.4.3 One USB port free for end-user expansion.
At least one USB port must be built into a mobile PC and not be provided solely by a docked mobile PC. This USB port can be either a high-power or low-power port, or it can be dynamically configurable at the discretion of the OEM, as provided for by Section 7 of the Universal Serial Bus Specification, Revision 1.1.
A3.4.4.4 CardBus slot (if implemented).
If Implemented, all CardBus implementations must comply with the requirements defined in B2.1, including information about the default initialization of the CardBus controller under Windows.
A3.4.4.5 System maintains mapping of IRQ Routing Register bits to system interrupt vectors for CardBus.
The system design must maintain the mapping of the CardBus controller’s IRQ Routing Register bits to system interrupt vectors. This means that when an interrupt is programmed in the controller to occur on the IRQx pin, the system’s IRQ routing causes the interrupt controller to generate the interrupt vector for IRQx and no other IRQ.
A3.4.4.6 IRQ connections for CardBus can be determined by using the 0805 register.
Windows uses the 0805 register on CardBus controllers to determine which ISA IRQs are connected to the controller. This register must engage (drive low when the IRQ is asserted) the corresponding ISA IRQ when programmed with a value. It must deselect the IRQ (float high) when programmed at zero (0). This behavior must be achieved without requiring the operating system to program any non-standard registers.
A3.4.4.7 Integrated graphics device minimum requirements: A3.4.4.7.1 2-D hardware acceleration, 640 × 480, low-resolution modes.
Mobile system supports display resolution of at least 640 × 480 with 256 colors. Windows requires a display resolution of at least 640 × 480 with 256 colors (8 bpp using a color look-up table) to run properly. Mobile systems that optionally have 3-D support must implement at least 16 bpp color.
A3.4.4.7.2 If 3-D is supported, 640 × 480 × 16 bpp; no minimum texture cache, alpha blending, hardware text mapping requirements.
Optional 3-D capabilities meet minimum requirements. For mobile systems, 3-D hardware is optional. If 3-D is supported, the mobile PC must meet all 3-D requirements at all supported resolutions up to and including the native display panel resolution of at least 640 × 480, and it must support a color depth of 16 bpp, with the following exceptions:
-
Support of per-pixel fog is not required; however, support of per-vertex fog is required.
-
Support of range-based or table-based fog is not required.
-
Support of 32-bit textures is not required; however, support of 16-bit textures is required.
-
Support of 32-bit Z buffers is not required; however, support of 16-bit Z buffers is required.
-
Support of Stencil buffers is not required.
-
Support of 32 bpp (ARGB 8:8:8:8) is not required.
-
Support of nonsquare power-of-two textures up to 10241024 for all textures operations is not required.
-
Support for square, power-of-two textures of sizes up to and including 256256 is required.
A3.4.4.7.3 Mobile PC resolution requirements.
Resolution and color depth requirements are limited to the capabilities of the integrated display panel when using an integrated panel or a simultaneous external display. Mobile systems that implement a single-chip, multihead configuration must meet the resolution and color depth requirements on the external display only up to the native resolution and color depth of the integrated display panel. Mobile PC systems that provide 3-D hardware acceleration must support a color depth of 16 bpp.
A3.4.4.7.4 No multiple adapter support required in mobile unit; multiple monitor support is optional.
For mobile PCs, multiple adapter support is not required unless the system supports single-chip, multihead, multiple-monitor capabilities, or the mobile PC supports a docking station with PCI expansion slots. If the docked mobile PC supports only Mini-PCI, the system is not required to support multiple-monitor requirements.
A3.4.4.7.5 DDC monitor detection required only for external graphics interface, with exceptions.
Mobile PC systems that support external displays must support DDC detection for external displays, with the following exceptions:
-
Mobile systems do not have to supply +5V to the VGA connector at any time.
-
The DVI connector must supply +5V only during operating system boot, when the user first enables external video, and when the system is actually outputting analog or digital video through the DVI connector.
-
Mobile systems that implement a single-chip, multihead, multimonitor configuration are not required to display the system boot screen on the external display. In this configuration, the expectation is that the external display will be active when the display driver is enabled and the system is configured for multimonitor operation. If the system is configured for operation with only the external display active, the boot screen must be displayed.
Note: Some display devices rely on the +5V to power their DDC circuitry, for Plug and Play detection, or both. It is recommended that a mobile PC provide a means to enable the +5V power when necessary.
A3.4.4.7.6. PCI or AGP 1.x or later. For systems supporting 3-D graphics hardware, performance equivalent of AGP 1x with GART is required.
Mobile systems that support 3-D require the performance equivalent of AGP. AGP implementations must support Graphics Address Remapping Table (GART) at a minimum. AGP equivalent implementations must support GART equivalent functionality. PCI implementations are not required to support GART.
A3.4.4.8 International Color Consortium (ICC) color profile and INF preinstalled if DDC detection cannot be used.
See B4.2.4.2
A3.4.5 ATA controllers and devices on mobile unit support ATA/33 or better
All ATA primary storage devices must support Ultra DMA at transfer rates of 33 MB per second or higher as defined in the ATA/ATAPI-5 standard.
A3.4.6 CD drive, if present, supports transfer rate of at least 1200 KB per second when fully on A3.4.7 Docking station requirements A3.4.7.1 Docked mobile PC meets Mobile PC system and BIOS requirements.
The docked mobile PC must meet the Logo Program requirement for multiple adapters and multiple monitors. This provides fully operational graphics capabilities in the mobile PC (either the LCD panel or external connector) in the event that a user adds another graphics adapter to the docking station.
A3.4.7.2 DELETED A3.4.7.3 Docking station supports warm docking and fail-safe docking.
Attaching or ejecting a mobile PC from a docking station must not require powering off the system and must not require a system reboot. The mobile PC’s ACPI BIOS must contain one or more _EJx methods to inform the operating system of which sleep states are supported for docking operations. For more information on the _EJx methods for Windows, refer to Section 6.3.2.I of ACPI 1.0b
The system must provide a mechanism for notifying the operating system before undocking a mobile PC, in combination with operating system capabilities and methods defined in Sections 5 and 6 of ACPI 1.0b.
There is no requirement for mechanical lockout to block the user from removing the mobile unit without operating-system notification.
A3.4.7.4 Enumerate, configure, and disable non-Plug and Play devices using ACPI-based methods.
The docked mobile PC must enumerate, configure, and disable non-Plug and Play devices using ACPI-based methods, and implement all notification events and docking control as follows.
The mobile PC’s ACPI BIOS must contain at least the following docking-related functions:
-
DCK_CAP must be set to 1 in the FADT table.
-
_Lxx methods must handle the dock insertion event and the Fail Safe Ejection notification. The _Lxx method must include a Notify to the dock object.
-
ACPI descriptions for ports located on the mobile PC and passed through the docking connector must include an _EJD method.
-
The _WAK method must perform a Notify to the dock object.
A dock object must be specified and must have a device named to represent the docking station, including:
-
_DCK method connecting and disconnecting the docking bus.
-
_STA method for checking the status of the dock.
-
_EJx methods to identify which sleep states docking can occur. If hot docking is implemented, the _EJ0 control method must not return until the ejection is complete, as stated in ACPI 1.0b section 6.3.2.
For additional information on ACPI docking implementation, refer to ACPI 1.0b and "ACPI Docking for Windows," at http://www.microsoft.com/hwdev/tech/onnow/ACPIdock.asp
Removable ATA devices in the docking station and in the mobile PC are required to report changes using ACPI-based methods.
A3.4.7.5 - See A3.4.7.1 A3.4.7.6 DELETED A3.4.7.7 Discrete PCI ATA controllers in mobile docking stations implement in PCI Native-Mode ATA.
Discrete ATA and ATAPI controllers that are implemented in mobile docking stations must comply with the PCI IDE Controller Specification, Revision 1.0, for native mode support. This requirement does not apply to controllers that are a part of the mobile PC’s chip set architecture.
A3.4.8 DELETED A3.4.9 DELETED A3.4.10 DELETED
|
