Re: [PATCH] Add CONFIG_ACPI_RELAXED_AML option

[Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>]

Hi!

> I must agree that this is a really bad idea.  Once we start allowing these
> kinds of errors to slip by, there is potentially no end to it.  It's a very
> slippery slope that will potentially plunge everyone into the same kind of
> BIOS abyss that ACPI was intended to solve in the first place.
> 
> Worse, there are situations where the AML interpreter cannot "guess" what
> the ASL/AML (BIOS) coder actually intended, i.e., there are multiple
> solutions to the problem.
> 
> What is really being proposed here is for Linux ACPI to be bug-for-bug
> compatible with Microsoft.  This is impossible to do deterministically
> because the MS interpreter is closed source.  The only standard that we have
> that we can code to is the ACPI specification, and this has to be the last
> word on the matter.

Okay, but we can try. We can for example ignore '*PNP101' and
understand it as 'PNP101', with printk("Star is not valid character in
device name"), which is way more helpufull than /proc/battery does not
exist.

I believe CONFIG_ACPI_RELAXED_AML is good idea.
								Pavel
-- 
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?


-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility 
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/