Bug 131015
Summary: | cpuspeed shouldn't require changes to config file to find the right driver | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Bastien Nocera <bnocera> |
Component: | cpuspeed | Assignee: | Dave Jones <davej> |
Status: | CLOSED RAWHIDE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | dbaron, notting, pfrields |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-07-16 01:53:06 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Bastien Nocera
2004-08-26 17:35:16 UTC
Also, we appear to have some modules built in, and some modules built as modules. :/ the modular/non-modular thing is intentional. Building them all in solves the problem of figuring out which module to load from userspace. Basically, by the time we get to userspace, we should have a valid driver setup, and if we haven't then the cpuspeed init script will load acpi-cpufreq as a fallback. The other drivers that /are/ modular are done so because probing for them is unsafe and has been known to cause problems on some boxes. in the majority of cases, you should never have to set the DRIVER line in the cpuspeed config. |