,
An update: We have been working on moving the ACPI code to the new 2.5
driver model, and are making good progress. That will be released as soon as
the all the drivers are converted. I'm somewhat torn as to even doing this
release, but since it should fix some blacklist problems and will serve as a
known good checkpoint in relation to the new OSPM code, I'm going ahead.
Due to our web people being on vacation, this release will not be going up
on developer.intel.com. It will be available only as a patch against 2.4.17,
from . I can email other release
packages by request, but you may just want to wait for the next release,
when they will all be up on the webpage, as usual.
Regards -- Andy
----------------------------------------
Summary of changes for this label: 12_18_01
1) Linux
Enhanced blacklist with reason and severity fields. Any table's signature
may
now be used to identify a blacklisted system.
Call _PIC control method to inform the firmware which interrupt model the OS
is using. Turn on any disabled link devices. (Note: _PRT usage will be in
the next release.)
Cleaned up busmgr /proc error handling (Andreas Dilger)
2) ACPI CA Core Subsystem:
Implemented ACPI 2.0 semantics for the "Break" operator (Exit from while
loop)
Completed implementation of the ACPI 2.0 "Continue",
"ConcatenateResTemplate",
"DataTableRegion", and "LoadTable" operators. All new ACPI 2.0 operators
are
now implemented in both the ASL compiler and the AML interpreter. The only
remaining ACPI 2.0 task is support for the String data type in the DerefOf
operator.
Fixed a problem with AcquireMutex where the status code was lost if the
caller
had to actually wait for the mutex.
Increased the maximum ASL Field size from 64K bits to 4G bits.
Completed implementation of the external Global Lock interfaces --
AcpiAcquireGlobalLock and AcpiReleaseGlobalLock. The Timeout and Handler
parameters were added.
Completed another pass at removing warnings and issues when compiling with
64-bit compilers. The code now compiles cleanly with the Intel 64-bit
C/C++ compiler. Most notably, the pointer add and subtract (diff) macros
have changed considerably.
Created and deployed a new ACPI_SIZE type that is 64-bits wide on 64-bit
platforms, 32-bits on all others. This type is used wherever memory
allocation and/or the C sizeof() operator is used, and affects the OSL
memory allocation interfaces AcpiOsAllocate and AcpiOsCallocate.
Implemented sticky user breakpoints in the AML debugger. (12_05_01)
Non-Debug Version: 64.7K Code, 5.3K Data, 70.0K Total
Debug Version: 136.2K Code, 55.6K Data, 191.8K Total
Current Release:
Non-Debug Version: 66.1K Code, 5.5K Data, 71.6K Total
Debug Version: 138.3K Code, 55.9K Data, 194.2K Total
3) ASL Compiler, version X2034:
Now checks for (and generates an error if detected) the use of a Break or
Continue statement without an enclosing While statement.
Successfully generated the compiler with the Intel 64-bit C compiler.
----------------------------
Andrew Grover
Intel/MPG/Mobile Arch Lab
andrew.grover@...
This patch is a follow-up to yesterday's "part 1" which is needed before
applying this patch. You can also find these patches at
!!!Please note: Do neither call pr_perf_get_p_state nor pr_perf_set_p_state
yet. Both perform an acpi-low-level write to an unitialized = random(?) =
dangerous address.
Only two things are missing now to complete P-States support: reading the
_PSS and _PCT packages. Is bm_evaluate_object the right call for that?
Dominik
Hi Paul and gang,
I am new to this list and couldn't find any info on this. I was
diagnosed with the EC0K problem. What is it and is there a fix? I've
already sent my DSDT to Paul.
Thanks!
Francis
> -----Original Message-----
> From: Diefenbaugh, Paul S [mailto:paul.s.diefenbaugh@...]
> Sent: Thursday, December 20, 2001 5:14 PM
> To: Yom, Francis
> Subject: RE: [ACPI] High fan with ACPI
> =20
> =20
> Francis:
> =20
> > Attached is my current dmesg. You'll notice that there is=20
> no mention=20
> > of thermal zones...
> =20
> You have the infamous 'ECOK' problem:
> dsutils-0343 [17] Ds_create_operand =20
> : Object name [\_SB_.OKEC] was not found in namespace
> dsutils-0505 [16] Ds_create_operands =20
> : While creating Arg 2 - AE_AML_NAME_NOT_FOUND
> ACPI: Processor[0]: C0 C1 C2
> =20
> Which is causing a miriad of other issues. Please send me=20
> your DSDT (sorry
> if you've already posted it).
> =20
> BTW - I didn't notice any issues related to "acpi_boot=3Don"?
> =20
> -- Paul
> =20