Localize one more variable to NPCI > 0 block. Fix ia64 build.

allow ACPI to compile without PCI support. fixes ia64 build.

Fix struct member prefix to be consistent. same code before and after.

Merge conflicts; STA methods and fields are not present anymore.

branches: 1.18.14;
Dump more FADT fields from ACPI 6.1.

branches: 1.17.6; 1.17.10;
fix unused variable warnings

branches: 1.16.8; 1.16.18; 1.16.22;
Scan for devices that are "hot-pluggable".

Include <dev/acpi/acpi_pci.h>.

acpi_pcidev_find_dev(): take struct acpi_devnode as a parameter.

Move the function that finds a device_t for the corresponding ACPI device
node from ACPIVERBOSE to the ACPI PCI code.

An _ADR object is not required for PCI root bridges. To solve
this, the structure acpi_pciinfo now tells whether the ACPI
device node is a PCI bridge, a regular PCI device, or both.

Problem reported by jmcneill@, who also suggested the solution.

ok jmcneill@, jruoho@

Do not discard ACPI PCI addresses with function number 0xFFFF: the
ACPI specification allows them (ACPI 4.0a, p. 200).

ok jruoho@

branches: 1.10.2; 1.10.4;
acpi_print_tree: print ACPI and PCI autoconf(9) device names.

ok jruoho@

Allow to dump the basic information at runtime with a flag to modload(8).
This can help when dealing with problem reports, as the user does not need
to reboot nor compile a kernel. Instead: 'modload -b dump=true acpiverbose'.

Dump MADT in ACPIVERBOSE.

Dump the whole FADT in ACPIVERBOSE.

Simplify the acpiverbose module.

Remove the acpiwmi(4) dump from the ACPIVERBOSE module. Instead of this
complex solution, just use aprint_debug(9) in the driver.

Move setting of acpi_verbose_loaded flag into the module's init routine.
This ensures that the flag is set even if the module was manually loaded
by the user rather than just auto-loaded.

branches: 1.3.2;
Update acpiverbose module to use module_autoload() rather than module_load().
Load the module right before each attempt to use its features, and let the
module subsystem handle unloading.

Remove trailing white space.

Extract ACPIVERBOSE into a kernel module. The module can be builtin
by defining 'options ACPIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

ACPIVERBOSE also includes code to dump acpi/wmi data.

allow ACPI to compile without PCI support. fixes ia64 build.

Fix struct member prefix to be consistent. same code before and after.

Merge conflicts; STA methods and fields are not present anymore.

branches: 1.18.14;
Dump more FADT fields from ACPI 6.1.

branches: 1.17.6; 1.17.10;
fix unused variable warnings

branches: 1.16.8; 1.16.18; 1.16.22;
Scan for devices that are "hot-pluggable".

Include <dev/acpi/acpi_pci.h>.

acpi_pcidev_find_dev(): take struct acpi_devnode as a parameter.

Move the function that finds a device_t for the corresponding ACPI device
node from ACPIVERBOSE to the ACPI PCI code.

An _ADR object is not required for PCI root bridges. To solve
this, the structure acpi_pciinfo now tells whether the ACPI
device node is a PCI bridge, a regular PCI device, or both.

Problem reported by jmcneill@, who also suggested the solution.

ok jmcneill@, jruoho@

Do not discard ACPI PCI addresses with function number 0xFFFF: the
ACPI specification allows them (ACPI 4.0a, p. 200).

ok jruoho@

branches: 1.10.2; 1.10.4;
acpi_print_tree: print ACPI and PCI autoconf(9) device names.

ok jruoho@

Allow to dump the basic information at runtime with a flag to modload(8).
This can help when dealing with problem reports, as the user does not need
to reboot nor compile a kernel. Instead: 'modload -b dump=true acpiverbose'.

Dump MADT in ACPIVERBOSE.

Dump the whole FADT in ACPIVERBOSE.

Simplify the acpiverbose module.

Remove the acpiwmi(4) dump from the ACPIVERBOSE module. Instead of this
complex solution, just use aprint_debug(9) in the driver.

Move setting of acpi_verbose_loaded flag into the module's init routine.
This ensures that the flag is set even if the module was manually loaded
by the user rather than just auto-loaded.

branches: 1.3.2;
Update acpiverbose module to use module_autoload() rather than module_load().
Load the module right before each attempt to use its features, and let the
module subsystem handle unloading.

Remove trailing white space.

Extract ACPIVERBOSE into a kernel module. The module can be builtin
by defining 'options ACPIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

ACPIVERBOSE also includes code to dump acpi/wmi data.

Fix struct member prefix to be consistent. same code before and after.

Merge conflicts; STA methods and fields are not present anymore.

branches: 1.18.14;
Dump more FADT fields from ACPI 6.1.

branches: 1.17.6; 1.17.10;
fix unused variable warnings

branches: 1.16.8; 1.16.18; 1.16.22;
Scan for devices that are "hot-pluggable".

Include <dev/acpi/acpi_pci.h>.

acpi_pcidev_find_dev(): take struct acpi_devnode as a parameter.

Move the function that finds a device_t for the corresponding ACPI device
node from ACPIVERBOSE to the ACPI PCI code.

An _ADR object is not required for PCI root bridges. To solve
this, the structure acpi_pciinfo now tells whether the ACPI
device node is a PCI bridge, a regular PCI device, or both.

Problem reported by jmcneill@, who also suggested the solution.

ok jmcneill@, jruoho@

Do not discard ACPI PCI addresses with function number 0xFFFF: the
ACPI specification allows them (ACPI 4.0a, p. 200).

ok jruoho@

branches: 1.10.2; 1.10.4;
acpi_print_tree: print ACPI and PCI autoconf(9) device names.

ok jruoho@

Allow to dump the basic information at runtime with a flag to modload(8).
This can help when dealing with problem reports, as the user does not need
to reboot nor compile a kernel. Instead: 'modload -b dump=true acpiverbose'.

Dump MADT in ACPIVERBOSE.

Dump the whole FADT in ACPIVERBOSE.

Simplify the acpiverbose module.

Remove the acpiwmi(4) dump from the ACPIVERBOSE module. Instead of this
complex solution, just use aprint_debug(9) in the driver.

Move setting of acpi_verbose_loaded flag into the module's init routine.
This ensures that the flag is set even if the module was manually loaded
by the user rather than just auto-loaded.

branches: 1.3.2;
Update acpiverbose module to use module_autoload() rather than module_load().
Load the module right before each attempt to use its features, and let the
module subsystem handle unloading.

Remove trailing white space.

Extract ACPIVERBOSE into a kernel module. The module can be builtin
by defining 'options ACPIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

ACPIVERBOSE also includes code to dump acpi/wmi data.

Merge conflicts; STA methods and fields are not present anymore.

branches: 1.18.14;
Dump more FADT fields from ACPI 6.1.

branches: 1.17.6; 1.17.10;
fix unused variable warnings

branches: 1.16.8; 1.16.18; 1.16.22;
Scan for devices that are "hot-pluggable".

Include <dev/acpi/acpi_pci.h>.

acpi_pcidev_find_dev(): take struct acpi_devnode as a parameter.

Move the function that finds a device_t for the corresponding ACPI device
node from ACPIVERBOSE to the ACPI PCI code.

An _ADR object is not required for PCI root bridges. To solve
this, the structure acpi_pciinfo now tells whether the ACPI
device node is a PCI bridge, a regular PCI device, or both.

Problem reported by jmcneill@, who also suggested the solution.

ok jmcneill@, jruoho@

Do not discard ACPI PCI addresses with function number 0xFFFF: the
ACPI specification allows them (ACPI 4.0a, p. 200).

ok jruoho@

branches: 1.10.2; 1.10.4;
acpi_print_tree: print ACPI and PCI autoconf(9) device names.

ok jruoho@

Allow to dump the basic information at runtime with a flag to modload(8).
This can help when dealing with problem reports, as the user does not need
to reboot nor compile a kernel. Instead: 'modload -b dump=true acpiverbose'.

Dump MADT in ACPIVERBOSE.

Dump the whole FADT in ACPIVERBOSE.

Simplify the acpiverbose module.

Remove the acpiwmi(4) dump from the ACPIVERBOSE module. Instead of this
complex solution, just use aprint_debug(9) in the driver.

Move setting of acpi_verbose_loaded flag into the module's init routine.
This ensures that the flag is set even if the module was manually loaded
by the user rather than just auto-loaded.

branches: 1.3.2;
Update acpiverbose module to use module_autoload() rather than module_load().
Load the module right before each attempt to use its features, and let the
module subsystem handle unloading.

Remove trailing white space.

Extract ACPIVERBOSE into a kernel module. The module can be builtin
by defining 'options ACPIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

ACPIVERBOSE also includes code to dump acpi/wmi data.

Dump more FADT fields from ACPI 6.1.

branches: 1.17.6; 1.17.10;
fix unused variable warnings

branches: 1.16.8; 1.16.18; 1.16.22;
Scan for devices that are "hot-pluggable".

Include <dev/acpi/acpi_pci.h>.

acpi_pcidev_find_dev(): take struct acpi_devnode as a parameter.

Move the function that finds a device_t for the corresponding ACPI device
node from ACPIVERBOSE to the ACPI PCI code.

An _ADR object is not required for PCI root bridges. To solve
this, the structure acpi_pciinfo now tells whether the ACPI
device node is a PCI bridge, a regular PCI device, or both.

Problem reported by jmcneill@, who also suggested the solution.

ok jmcneill@, jruoho@

Do not discard ACPI PCI addresses with function number 0xFFFF: the
ACPI specification allows them (ACPI 4.0a, p. 200).

ok jruoho@

branches: 1.10.2; 1.10.4;
acpi_print_tree: print ACPI and PCI autoconf(9) device names.

ok jruoho@

Allow to dump the basic information at runtime with a flag to modload(8).
This can help when dealing with problem reports, as the user does not need
to reboot nor compile a kernel. Instead: 'modload -b dump=true acpiverbose'.

Dump MADT in ACPIVERBOSE.

Dump the whole FADT in ACPIVERBOSE.

Simplify the acpiverbose module.

Remove the acpiwmi(4) dump from the ACPIVERBOSE module. Instead of this
complex solution, just use aprint_debug(9) in the driver.

Move setting of acpi_verbose_loaded flag into the module's init routine.
This ensures that the flag is set even if the module was manually loaded
by the user rather than just auto-loaded.

branches: 1.3.2;
Update acpiverbose module to use module_autoload() rather than module_load().
Load the module right before each attempt to use its features, and let the
module subsystem handle unloading.

Remove trailing white space.

Extract ACPIVERBOSE into a kernel module. The module can be builtin
by defining 'options ACPIVERBOSE' in the kernel config file (no change
from current behavior), or it can be loaded at boot time on those
architectures that support the boot loader's "load" command.

ACPIVERBOSE also includes code to dump acpi/wmi data.