23 August 2013. Summary of changes for version 20130823:
This release is available at https://acpica.org/downloads
1) ACPICA kernel-resident subsystem:
Implemented support for host-installed System Control Interrupt (SCI) handlers. Certain ACPI functionality requires the host to handle raw SCIs. For example, the "SCI Doorbell" that is defined for memory power state support requires the host device driver to handle SCIs to examine if the doorbell has been activated. Multiple SCI handlers can be installed to allow for future expansion. New external interfaces are AcpiInstallSciHandler, AcpiRemoveSciHandler; see the ACPICA reference for details. Lv Zheng, Bob Moore. ACPICA BZ 1032.
Operation region support: Never locally free the handler "context" pointer. This change removes some dangerous code that attempts to free the handler context pointer in some (rare) circumstances. The owner of the handler owns this pointer and the ACPICA code should never touch it. Although not seen to be an issue in any kernel, it did show up as a problem (fault) under AcpiExec. Also, set the internal storage field for the context pointer to zero when the region is deactivated, simply for sanity. David Box. ACPICA BZ 1039.
AcpiRead: On error, do not modify the return value target location. If an error happens in the middle of a split 32/32 64-bit I/O operation, do not modify the target of the return value pointer. Makes the code consistent with the rest of ACPICA. Bjorn Helgaas.
Example Code and Data Size: These are the sizes for the OS-independent acpica.lib produced by the Microsoft Visual C++ 9.0 32-bit compiler. The debug version of the code includes the debug output trace mechanism and has a much larger code and data size.
Non-Debug Version: 96.7K Code, 27.1K Data, 123.9K Total
Debug Version: 184.4K Code, 76.8K Data, 261.2K Total
Non-Debug Version: 96.2K Code, 27.1K Data, 123.3K Total
Debug Version: 185.4K Code, 77.1K Data, 262.5K Total
2) iASL Compiler/Disassembler and Tools:
AcpiDump: Implemented several new features and fixed some problems:
1) Added support to dump the RSDP, RSDT, and XSDT tables.
2) Added support for multiple table instances (SSDT, UEFI).
3) Added option to dump "customized" (overridden) tables (-c).
4) Fixed a problem where some table filenames were improperly constructed.
5) Improved some error messages, removed some unnecessary messages.
iASL: Implemented additional support for disassembly of ACPI tables that contain invocations of external control methods. The -fe<file> option allows the import of a file that specifies the external methods along with the required number of arguments for each -- allowing for the correct disassembly of the table. This is a workaround for a limitation of AML code where the disassembler often cannot determine the number of arguments required for an external control method and generates incorrect ASL code. See the iASL reference for details. ACPICA BZ 1030.
Debugger: Implemented a new command (paths) that displays the full pathnames (namepaths) and object types of all objects in the namespace. This is an alternative to the namespace command.
Debugger: Implemented a new command (sci) that invokes the SCI dispatch mechanism and any installed handlers.
iASL: Fixed a possible segfault for "too many parent prefixes" condition. This can occur if there are too many parent prefixes in a namepath (for example, ^^^^^^PCI0.ECRD). ACPICA BZ 1035.
Application OSLs: Set the return value for the PCI read functions. These functions simply return AE_OK, but should set the return value to zero also. This change implements this. ACPICA BZ 1038.
Debugger: Prevent possible command line buffer overflow. Increase the size of a couple of the debugger line buffers, and ensure that overflow cannot happen. ACPICA BZ 1037.
iASL: Changed to abort immediately on serious errors during the parsing phase. Due to the nature of ASL, there is no point in attempting to compile these types of errors, and they typically end up causing a cascade of hundreds of errors which obscure the original problem.
Would it be possible to use the following patch? Or, a file
very similar to it -- I do not know if the wording of the first
paragraph would be acceptable or not, so it may need changing.
The reason I ask is that this makes life much simpler for the
various Linux distributions. In the Unix(tm) versions provided
at acpica.org, _most_ files have a nicely done header that lays
out the licensing. In fact, in the patch below, everything from
"Copyright..." to the end is from that header.
However, not all files have the header (e.g., the AAPITS tests,
and some of the .sh or Makefiles used) which makes both Debian
and Fedora a little nervous. The FAQ clearly states the GPL
can be used, but the source code does not always repeat it.
I am currently the primary uploader for Debian of a package called
'acpica-tools' that provides all of the user space commands from
the ACPICA source trees. Further, when the package is built, the
ASLTS and AAPITS tests are run against the commands to help with
QA. I am doing the same work for Fedora, and trying to keep both
distributions (and in turn, their derivatives) as up-to-date as
Having this one file in the ACPICA provided source trees for
Unix(tm) would help make things much clearer for both of these
Thanks in advance for your consideration.
LICENSE | 44 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 44 insertions(+)
create mode 100644 LICENSE
diff --git a/LICENSE b/LICENSE
new file mode 100644
@@ -0,0 +1,44 @@
+Licensing for Linux Systems:
+Whether explicitly stated in the source code for this software or not,
+this software is distributed under the terms of the GNU General Public
+License ("GPL") version 2 as published by the Free Software Foundation.
+This is in accordance with the following license from Intel Corporation
+that should be a part of all source code files:
+ Copyright (C) 2000 - 2013, Intel Corp.
+ All rights reserved.
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+ notice, this list of conditions, and the following disclaimer,
+ without modification.
+ 2. Redistributions in binary form must reproduce at minimum a disclaimer
+ substantially similar to the "NO WARRANTY" disclaimer below
+ ("Disclaimer") and any redistribution must be conditioned upon
+ including a substantially similar Disclaimer requirement for further
+ binary redistribution.
+ 3. Neither the names of the above-listed copyright holders nor the names
+ of any contributors may be used to endorse or promote products
+ from this software without specific prior written permission.
+ Alternatively, this software may be distributed under the terms of the
+ GNU General Public License ("GPL") version 2 as published by the Free
+ Software Foundation.
+ NO WARRANTY
+ THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+ "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
+ LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR
+ A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
+ HOLDERS OR CONTRIBUTORS BE LIABLE FOR SPECIAL, EXEMPLARY, OR
+ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+ STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
+ IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+ POSSIBILITY OF SUCH DAMAGES.
Red Hat, Inc.
Ladies and Gentlemen,
APSoft Germany released new version of ACPIScope - ACPI exploration tool for Windows OS (http://www.tssc.de/products/tools/acpiscope/default.htm).
ACPIScope provides an access to all three sources of ACPI information on Windows computer:
* OSPM driver
* BIOS ACPI tables
* ACPI tables cached in Windows registry
Please feel free to download and try product free for two weeks. Please feel free to send us suggestions for the product improvements to mailto:firstname.lastname@example.org.
With best regards,