Duran, Leo wrote:
OK, lets' take K8 processor performance states (p-states) as an example:
BIOS, which should know 'best' about a given platform, needs to
communicate to the OS what 'voltage' (VID code) is correct for given
'frequency' (FID),
and it can do that via ACPI processor tables (_PSS). Otherwise, OS code
is left with having to manage a HUGE amount 'specifics' (processor
models), and endless driver revisions to account for new parts.
So, one can argue that there's merit on having ACPI, it's just a shame
when BIOS doesn't get it right! (thus the justification for lack of
'trust'... the same can probably be said about other BIOS issues, not
just ACPI)
That's pretty much it in a nutshell... Since most BIOS are largely
tested and qualified only on That Other OS, Linux often gets the short
end of the stick. We have a long history of running into BIOS bugs, and
having to work around them. We've learned the hard way that programming
the "bare metal" is often the only reliable way to get things done.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]