Bytes were reversed for these types. Fortunately, these are mostly
used for reserved fields. UINT24 is used for actual data in one
field of the SRAT (ProximityDomainHi).
These operators were missing from the ACPI specification and thus
did not get pulled into this utility. ACPI 5.0 spec adds them,
and they are added to AcpiHelp.
Optimizations like -O2 are seen to cause issues with some compilers.
Remove unneeded defines like DEBUG, _CONSOLE, etc.
Add _GNU_SOURCE to the Linux makefiles.
The only acpica tool that requires multithread support is
acpiexec. Along with previous changes to the actual source code,
this change removes unnecessary use of threading libraries.
It takes some effort to disable the MS language extensions because
of bugs in the MS headers, and the MS remapping of the low I/O
functions (open, read, write, etc.)
Conditionally compile the multi-thread support so that threading
libraries will not be linked if not necessary. The only tool
that requires multi-thread support is AcpiExec.
Disable language extensions where possible for maximum portability.
Unfortunately, when MS system includes are used, this option
cannot be used (oswinxf.c)
Update purpose of the makefile and add a warning that these makefiles
are only suitable for generation within the native ACPICA directory
structure (which is different than Linux, for example.)
Update purpose of the makefile and add a warning that the makefiles
are only suitable for use on Linux, with the Linux directory
structure (different than the native ACPICA directory structure.)
We can only sort the _TSS return package if there is no _PSS in the
same scope. This is because if _PSS is present, the ACPI specification
dictates that the _TSS Power Dissipation field is to be ignored, and
therefore some BIOSs leave garbage values in the _TSS Power field(s).
In this case, it is best to just return the _TSS package as-is.
Runtime option can be used to disable return value repair if this
is causing a problem on a particular machine. Also added an option
to AcpiExec (-dr) to set this disable flag.
Now, only allow "SSDT" "OEM", and a null signature.
History:
1) Originally, we checked the table signature for "SSDT" or "PSDT".
2) We added support for OEMx tables, signature "OEM".
3) Valid tables were encountered with a null signature, so we just
gave up on validating the signature, (05/2008).
4) We encountered non-AML tables such as the MADT, which caused
interpreter errors and kernel faults. So now, we once again allow
only "SSDT", "OEMx", and now, also a null signature. (05/2011).
