Remove references to acpinames(8) from various manual pages.

Sync ACPICA with Intel's version 20180508 (from previously 20170831).

Tons of fixes and improvements.

For detailed list, please see sys/contrib/dev/acpica/changes.txt.

Sync ACPICA with Intel's version 20161117.

* Fixed regression introduced in 20160729 in the table manager. Also,
add a new public interface, AcpiPutTable().

* Fix a problem where runtime implicit

Sync ACPICA with Intel's version 20161117.

* Fixed regression introduced in 20160729 in the table manager. Also,
add a new public interface, AcpiPutTable().

* Fix a problem where runtime implicit conversion as incorrectly
disabled for some ASL operators.

* Various fixes and improvements for iasl(8).

* In acpixtract(8), add handling for both LF and CR/LF line
termination to accept acpidump output from any system.

* In acpibin(8), add new -a and -o options.

For a more detailed list, please see sys/contrib/dev/acpica/changes.txt.

show more ...

Sync ACPICA with Intel's version 20160108.

This includes the 20151218 upgrade which we had to revert again because
of a bug found by tkusumi. The only major change in 20160108 is a fix
for this bug.

Sync ACPICA with Intel's version 20160108.

This includes the 20151218 upgrade which we had to revert again because
of a bug found by tkusumi. The only major change in 20160108 is a fix
for this bug.

20151218 changes:

* Execute "module-level code" as ACPI tables are loaded into the
namespace during initialization and install the default operation
region handlers for the SystemMemory, SystemIO and PCI_Config
address spaces before any ACPI tables are loaded (in order to
enable module-level code to access these address spaces). Also,
several changes to the internal _REG support and to utilities
in conjunction with these changes.

20160108 changes:

* Fixed a regression introduced in version 20151218 concerning the
execution of so-called module-level ASL/AML code. Namespace objects
created under a module-level If() construct were not properly/fully
entered into the namespace and could cause an interpreter fault when
accessed.

* Fixed a problem with the compilation of the GpioIo and GpioInt resource
descriptors. The _PIN field name was incorrectly defined to be an array
of 32-bit values, but the _PIN values are in fact 16 bits each. This
would cause incorrect bit width warnings when using Word (16-bit) fields
to access the descriptors.

Additionally, some minor fixes, features etc. were added.

For a more detailed list, please see sys/contrib/dev/acpica/changes.txt.

Tested-by: tkusumi

show more ...

Revert "Sync ACPICA with Intel's version 20151218."

This reverts commit 2762423991074ed996c5c4488491cb3ef18c25ea.

It caused a panic on one box and enabling module-level code grouping
again didn't f

Revert "Sync ACPICA with Intel's version 20151218."

This reverts commit 2762423991074ed996c5c4488491cb3ef18c25ea.

It caused a panic on one box and enabling module-level code grouping
again didn't fix that, so it needs further investigation first.

show more ...

Sync ACPICA with Intel's version 20151218.

* Execute "module-level code" as ACPI tables are loaded into the
namespace during initialization and install the default operation
region handlers for

Sync ACPICA with Intel's version 20151218.

* Execute "module-level code" as ACPI tables are loaded into the
namespace during initialization and install the default operation
region handlers for the SystemMemory, SystemIO and PCI_Config
address spaces before any ACPI tables are loaded (in order to
enable module-level code to access these address spaces). Also,
several changes to the internal _REG support and to utilities
in conjunction with these changes.

* Various other fixes and features.

For a more detailed list, please see sys/contrib/dev/acpica/changes.txt.

show more ...

Add a acpicall(8) utility for debugging and tweaking purposes.

It is based on ports' sysutils/acpi_call (from Maxim Ignatenko) with
a few changes by me:

* Rename acpi_call -> acpicall.

* Ioctl han

Add a acpicall(8) utility for debugging and tweaking purposes.

It is based on ports' sysutils/acpi_call (from Maxim Ignatenko) with
a few changes by me:

* Rename acpi_call -> acpicall.

* Ioctl handling is in the main acpi.ko module.

* To enable it, the debug.acpi.allow_method_calls tunable needs to
be set.

* In acpi_call, the mandatory -p option was used to pass the method's
namespace path. I removed the option and made the path acpicall(8)'s
argument.

* Wrote a manual page and cleaned up a bit.

The separate acpiio_mcall.h file was added because ACPIIO_DO_MCALL's
argument struct uses ACPICA types, so it needs acpi.h which acpiio.h
(a public header used by some ports) so far didn't need. So to avoid
any hassle, I put the ACPIIO_DO_MCALL ioctl into a separate header
(it's only used by acpicall(8) anyway).

The changes to kdump(1) and truss(1) are to include and build with
acpi.h.

Tested-by: tollens

show more ...

kernel: Sync ACPICA with Intel's version 20140325.

As far as I can see, the most important change is a fix for the auto-
serialization of control methods so that the currently executing AML
SyncLeve

kernel: Sync ACPICA with Intel's version 20140325.

As far as I can see, the most important change is a fix for the auto-
serialization of control methods so that the currently executing AML
SyncLevel is ignored when invoking such a method. This fixes an issue
seen in some systems showing AE_AML_MUTEX exceptions since 20140214
which had to set hw.acpi.auto_serialize_methods to 0 to work around
the issue.

This was actually reported for DragonFly by Andrey Oktyabrskiy (see
http://lists.dragonflybsd.org/pipermail/users/2014-February/109376.html).

See sys/contrib/dev/acpica/changes.txt for a complete list of all
changes.

show more ...

Add some manual pages for the ACPICA utilities provided by Intel.

For now, just list the options and their descriptions (taken from the
usages).