> On Wed, 2006-02-01 at 20:35 -0500, Brown, Len wrote:
> > Re: bad timing
> > If the BIOS advertises C2 latency > 100usec, then the BIOS
> > and the system do not support C2.
> > If the BIOS advertises C3 latency > 1000usec, then the BIOS
> > and the system do not support C3.
> > This isn't just a suggestion, it is the standard method
> > that the spec provides the BIOS to tell the OS to NOT USE these states.
>
> Isn't there any other way to tell the operating system that the C2/C3
> states are unusable (e.g. by simply telling they're not there?). This
> looks so obfuscated...
Hi!
The problem is that the table (RSDT) has a fixed format and the values have
reserved positions. Putting 0 there would mean zero (unmeasureble) latency,
which would be the best case, of course. So to disable the feature, "out of
range" method was selected. Yes, it would be nice to have some "special" value
there, like FFFF, but it is not a common practice.
With regards, Pavel Troller
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
