Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
linux
Commits
10f44fc4
Commit
10f44fc4
authored
Sep 29, 2003
by
Dave Jones
Committed by
Dave Jones
Sep 29, 2003
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[CPUFREQ] Fix ordering in kconfig.
parent
ab2d870e
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
6 deletions
+6
-6
arch/i386/kernel/cpu/cpufreq/Kconfig
arch/i386/kernel/cpu/cpufreq/Kconfig
+6
-6
No files found.
arch/i386/kernel/cpu/cpufreq/Kconfig
View file @
10f44fc4
...
...
@@ -78,21 +78,21 @@ config X86_POWERNOW_K6
If in doubt, say N.
config X86_POWERNOW_K
8
tristate "AMD
Opteron/Athlon64
PowerNow!"
config X86_POWERNOW_K
7
tristate "AMD
Mobile Athlon/Duron
PowerNow!"
depends on CPU_FREQ_TABLE
help
This adds the CPUFreq driver for mobile AMD
Opteron/Athlon64
processors.
This adds the CPUFreq driver for mobile AMD
K7 mobile
processors.
For details, take a look at linux/Documentation/cpu-freq.
If in doubt, say N.
config X86_POWERNOW_K
7
tristate "AMD
Mobile Athlon/Duron
PowerNow!"
config X86_POWERNOW_K
8
tristate "AMD
Opteron/Athlon64
PowerNow!"
depends on CPU_FREQ_TABLE
help
This adds the CPUFreq driver for mobile AMD
K7 mobile
processors.
This adds the CPUFreq driver for mobile AMD
Opteron/Athlon64
processors.
For details, take a look at linux/Documentation/cpu-freq.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment