Completed investigation and implementation of the
call-by-reference mechanism for control method arguments.

Fixed a problem where a store of an object into an indexed
package could fail if the store occurs within a different
method than the method that created the package.

Fixed a problem where the ToDecimal operator could return
incorrect results.

Fixed a problem where the CopyObject operator could fail
on some of the more obscure objects (e.g., Reference objects.)

Improved the output of the Debug object to display buffer,
package, and index objects.

Fixed a problem where constructs of the form "RefOf (ArgX)"
did not return the expected result.

Added permanent ACPI_REPORT_ERROR macros for all instances of the
ACPI_AML_INTERNAL exception.

The attached patch updates the acpi4asus driver to 0.27 through the
following changes:
- add support for M1300A, S5200N, L8400L,
- remove WLED support for certain models, since it is not controlled by
  AML,
- add LCD backlight switching for L2E / L3H,
- C99 initializers,
- generic LED handlers,
- the output of ASYM method to provide battery state information (might be
  more accurate under certain conditions) in /proc/acpi/asus/info,
- fix several oddities, various clean-ups and other minor changes.

The patch itself is quite big, which is mostly due to the C99 initializers
and the fact that diff doesn't like moving code around.

This has been compile-tested in various configurations, the substantive
changes were discussed on the acpi4asus mailing list.

The code should apply to current bk (both for 2.4 and 2.6). The patch is
also available here:
http://hell.org.pl/~sziwan/asus/acpi4asus-0.26-0.27.diff

Thanks to all the contributors (notably Pontus Fuchs) to this release.

Fix remote chance of invalid buffer access in write_video.
Support alternate HCI method path (recent "Phoenix BIOS" Toshiba's).
Signal more proc-write errors.
On proc-reads, report errors via printk instead of proc output.
Add log level and driver name prefix to all printk's.
Add missing __init and __exit function attributes.
Be explicit about vars for which code relies on zero-init of BSS.

from Martin Hicks

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

from Dominik Brodowski

Add support for _PDC to the ACPI processor "Performance States library" 
(perflib). If this field is empty, a bogus entry is passed to the _PDC
method so that the default (io) access is returned again. This patch
is partly based on David Moore's patch to
arch/i386/kernel/cpu/cpufreq/acpi.c, sent to the cpufreq mailing list on
June 24th, 2003.

and the ACPI Processor P-States driver.

from Dominik Brodowski

drivers/acpi/processor.c -- it's the same for all lowlevel drivers.

By doing so, the lowlevel drivers no longer need
to have access to struct acpi_processor.

from Dominik Brodowski

  so that it can be used by various low-level drivers
  (centrino, acpi-io, powernow-k{7,8}, ...)
  from Dominik Brodowski

  http://bugzilla.kernel.org/show_bug.cgi?id=1766

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

Fix a horribly wrong memcpy instruction in cpufreq_update_policy which
caused it to oops.

- remove unnecessary usage of flags.performance
- remove double check of _PPC in acpi-cpufreq driver as it's handled in
  drivers/acpi/processor.c already
- remove unneeded EXPORT_SYMBOL
- allocation of memory only for probed CPUs
- add unregistration function to the core
- fix OOPS when PST has core_frequency values of zero
- fix cpufreq_get() output
- fix /proc/acpi/processor/*/performance write support [deprecated]

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

updates the _PPC handling. It is handled as a CPUfreq
policy notifier which adjusts the maximum CPU speed
according to the current platform limit.

from Dominik Brodowski

The acpi cpufreq driver includes a test at startup which detects whether
ACPI P-States are supported on any CPU, and whether transitions work.
However, this test is faulty: it is only run _after_ the acpi driver is
registered, causing race situations. Also, it doesn't save anything _as_ the
driver is already registered. So, it can safely be removed.

	from Dominik Brodowski

The current algorithm used by Linux ACPI for passive thermal management has
two shortcomings:

- if increasing the CPU processing power as a thermal situation goes away,
  throttling states are decreased later than performance states. This is
  not wise -- it should be the opposite ordering of going "up".

- only if the ACPI CPUfreq driver is used, performance states are used.
  A generalized approach would offer passive cooling even if the ACPI
  P-States cpufreq driver cannot be used (faulty BIOS, FixedHW access, etc.)

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

from Jes Sorensen

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

        from ia64 via Alex Williamson

	from Jes Sorensen

	from Jes Sorensen

  from Bjorn Helgaas

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

The purpose of this release is primarily to update the copyright years
in each module, thus causing a huge number of diffs.  There are a few
small functional changes, however.

Improved error messages when there is a problem finding one or more of
the required base ACPI tables

Reintroduced the definition of APIC_HEADER in actbl.h

Changed definition of MADT_ADDRESS_OVERRIDE to 64 bits (actbl.h)

Removed extraneous reference to NewObj in dsmthdat.c

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

	http://bugzilla.kernel.org/show_bug.cgi?id=1349
	from David Shaohua Li and Venatesh Pallipadi

into intel.com:/home/lenb/src/linux-acpi-test-2.6.1

into lips.borg.umn.edu:/export/music/bkroot/xfs-linux-2.6

We must not mark the process TASK_STOPPED early, because
that might allow a signal to wake it up before we actually
got to the "wake_up_forked_process()" state. Total confusion
would happen.

Make wake_up_forked_process() verify the new world order.

into home.osdl.org:/home/torvalds/v2.5/linux