diff options
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/feature-removal-schedule.txt | 22 |
1 files changed, 0 insertions, 22 deletions
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt index 0599a0c7c026..092c65dd35c2 100644 --- a/Documentation/feature-removal-schedule.txt +++ b/Documentation/feature-removal-schedule.txt | |||
@@ -196,28 +196,6 @@ Who: Adrian Bunk <bunk@stusta.de> | |||
196 | 196 | ||
197 | --------------------------- | 197 | --------------------------- |
198 | 198 | ||
199 | What: ACPI hooks (X86_SPEEDSTEP_CENTRINO_ACPI) in speedstep-centrino driver | ||
200 | When: December 2006 | ||
201 | Why: Speedstep-centrino driver with ACPI hooks and acpi-cpufreq driver are | ||
202 | functionally very much similar. They talk to ACPI in same way. Only | ||
203 | difference between them is the way they do frequency transitions. | ||
204 | One uses MSRs and the other one uses IO ports. Functionaliy of | ||
205 | speedstep_centrino with ACPI hooks is now merged into acpi-cpufreq. | ||
206 | That means one common driver will support all Intel Enhanced Speedstep | ||
207 | capable CPUs. That means less confusion over name of | ||
208 | speedstep-centrino driver (with that driver supposed to be used on | ||
209 | non-centrino platforms). That means less duplication of code and | ||
210 | less maintenance effort and no possibility of these two drivers | ||
211 | going out of sync. | ||
212 | Current users of speedstep_centrino with ACPI hooks are requested to | ||
213 | switch over to acpi-cpufreq driver. speedstep-centrino will continue | ||
214 | to work using older non-ACPI static table based scheme even after this | ||
215 | date. | ||
216 | |||
217 | Who: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com> | ||
218 | |||
219 | --------------------------- | ||
220 | |||
221 | What: /sys/firmware/acpi/namespace | 199 | What: /sys/firmware/acpi/namespace |
222 | When: 2.6.21 | 200 | When: 2.6.21 |
223 | Why: The ACPI namespace is effectively the symbol list for | 201 | Why: The ACPI namespace is effectively the symbol list for |