RE: ACPI_STRICT_COMPLIANCE (was RE: RE: ACPI -- Workaround forbroken DSDT)

[Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>]

On Wed, 2004-02-11 at 13:04, Cagle, John (ISS-Houston) wrote:

> I agree.  This should make a lot of users happy, since the distro's will
> work out-of-the-box without modification (at least on those machines
> with known workarounds implemented in the ACPI driver), yet the OEMs can
> still test for strict compliance by recompiling the kernel.  Better than
> that would be a kernel command line option to do the same thing.
> ACPI_STRICT=ON?

I think you're right.  If STRICT added code, then a re-build would be
appropriate, b/c the default kernel shouldn't be burdened with extra
code for validation or compliance testing.  However, STRICT would
generally disable code -- so we might as well make it accessible by
using a boot option instead of a build option.  Say...

acpi=strict
  Disable workarounds in Linux for platforms that are not
  strictly ACPI compliant.  This may cause additional warnings
  or cause your system not to boot.


if (acpi_strict)
	a compliance check or warning that is known to fail
	on some systems.

if (!acpi_strict)
	a workaround that is known to be necessary
	on some non-compliant systems, eg. RELAXED_AML

-Len




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click