Difference between revisions of "ACPI"
Jump to navigation
Jump to search
(→Generic part of DSDT: fix wrong link format) |
m (→PCI root bus _CRS method: add some i945 hints) |
||
| Line 113: | Line 113: | ||
=== PCI root bus _CRS method === | === PCI root bus _CRS method === | ||
Windows needs to know the actual decode ranges for PCI root bus (and any other). Windows needs to know platform independent way, how is I/O routed on PCI0 bus (and other busses). For K8 | Windows needs to know the actual decode ranges for PCI root bus (and any other). Windows needs to know platform independent way, how is I/O routed on PCI0 bus (and other busses). | ||
* For K8 this means to read the I/O and MMIO routing registers (same as '''k8resdump''' provides) and use them to create ACPI objects. The actual PCI regs are read in acpi-k8 in modelf and stored as SSDT table. The k8-util.asl code will construct the resources from that SSDT table. One can use the k8-util.asl code which will construct the resource objects. Check the ASUS M2V-MX mainboard ACPI code. | |||
One can use the k8-util.asl code which will construct the resource objects. Check the ASUS M2V-MX mainboard ACPI code. | * For i945 the required registers are read in the ASL code in northbridge/intel/i945/acpi/i945_hostbridge.asl. | ||
=== DSDT debugging === | === DSDT debugging === | ||