Aubrey wrote: > For P-state driver, I have one suggestion. There are still some old > machines which support early ACPI specs but not support P-state. > We should not ignore this kind of machine. So IMHO P-state driver should > check the version of ACPI and doesn't make unnecessary warning. It's a bit difficult to tell what version of ACPI a BIOS has been "written for"; there's no version stamp on a BIOS saying "compliant with ACPI version x.xx". Certainly we shouldn't generate warnings when a feature simply isn't supported, though.
> Another thing is ACPICA, I didn't dig into too much, but found the > version in the solaris is some different from the one on intel website. > How often does it sync-up with Intel ACPI CA releases? I do sync-up integrations of the ACPI CA source into Solaris whenever there's a critical-mass of new features, bug fixes or a high-severity bug-fix. I do integrate every source drop into an experimental workspace and sanity-test it in-between. Historically, this used to mean integrating a new drop into Solaris Nevada about 2-3 times a year, though it's been a year since the last such integration. There are some outstanding issues with the latest source drop I received from Bob Moore before he went on sabbatical, so I have not integrated the latest Intel sources yet. What version did you find on the Intel website? We're currently at 20060721 in Solaris Nevada. Dana
