An internal COM port header can be used as a debug port solution if the COM port is not exposed to the end user and does not use the I/O addresses listed in this table; these listed addresses must be claimed in the BIOS but not used. The relocated I/O address must be reported in the ACPI Debug Port table.
Systems that use the 8042 controller internally can use the related restricted addresses if the 8042 flag is set to 1 in the ACPI FADT. The 8042 flag must be set to 0 in systems that do not include an 8042 controller.
Systems can provide Super I/O-based IrDA support through the year 2001. Both desktop and mobile PCs can use the 8042 controller internally, but must not include external PS/2 connectors. Legacy-free systems that use the 8042 controller internally must set the 8042 flag to 1 in the ACPI FADT.
Windows Me: A system that does not have an 8042 controller must reserve I/O addresses 0060 and 0064 as reserved motherboard resources. Failure to reserve these I/O addresses will result in display of a false device in Device Manager.
A4.1.4 Support required interrupts
INT 8, INT 9, INT 10, INT 11, INT 13, INT 19, INT 1B, and INT 23
INT 15 subfunctions AH=C0, 4F, 87, 88 and AX=C2xx, E820, E801
INT 16 subfunctions AH=00h, 01h, 02h, 10h, 11h, 12h
INT 1A subfunctions AH=0x and AX=B1xx
See details in Table 2 at http://www.microsoft.com/hwdev/NewPC/LF.htm.
A4.1.5 Legacy-free debug interface per Debug Port Specification and FAQ A1.5.16
[SYS-0046; SDG3:15; FAQ A1.5.16]
A4.1.6 When 8042 is not present, A20M# is de-asserted (pulled high) or removed, with no way to mask the A20 address line
If A20M# generation logic (8042) is not present in the system, A20M# must be terminated in a deasserted state to the processor. If 8042 is present, connect in the standard legacy manner.
A4.1.7 Interrupt handlers preserve values in all registers
As described in A1.4.9.
A4.1.8 BIOS initializes USB Host Controller during boot process
The USB host controller must be in IRQ mode for keyboard and mouse input during real mode and safe mode. However, this can potentially cause the system to stop working when the system is running Windows 2000 if the interrupt is shared with the boot device and the host controller generates an IRQ before the USB ISR is chained.
The solution is for the BIOS to add logic to the ACPI Enable routine to turn off the IRQ-enable bit in PCI Config space for the USB host controller.
A4.5.2 Early legacy-free systems [Clarification]
Removal of legacy components from the system involves two considerations:
The component is removed from the user’s perspective -- for example, slots, ports, and so on.
The operating system doesn't detect the presence of the component.
For example, "No FDC" means that the operating system does not detect the presence of the FDC and nothing uses the related restricted addresses.
However, the physical internal part does not need to be removed -- for example, removal of the Super I/O chip is not required; however, the physical ports must not be present on the system or detected by the operating system.
A4.5.3 CD or DVD drive requirement [Clarification]
For legacy-free mobile PCs, form-factor/size issues may preclude providing a built-in CD or DVD drive. In such cases, the requirement to include a CD or DVD drive can be met by offering external CD/DVD products that the user can choose to purchase separately and that attach to the mobile PC, docking system, or port replicator through an interface that allows the CD or DVD drive to act as a boot device.
In addition, systems designed to exclude user access to removable media do not have to meet the requirement to include a CD or DVD device. However, all systems (including those that do not ship with a CD or DVD device) must still comply with the requirement for BIOS boot support.
FAQ date: September 1999
A4.5.4 Debug solutions for Non-Legacy PCs [Clarification]
See FAQ A1.5.16.
A4.R Legacy-Free PC System - Future Requirements
Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/system/