Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
linux-davinci
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Redmine
Redmine
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Metrics
Environments
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
linux
linux-davinci
Commits
c2672f62
Commit
c2672f62
authored
Nov 20, 2007
by
Paul Mundt
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
sh: Add the
SH-5
cpu type symbolic names.
Signed-off-by:
Paul Mundt
<
lethal@linux-sh.org
>
parent
d1839136
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
1 deletion
+3
-1
arch/sh/kernel/setup.c
arch/sh/kernel/setup.c
+3
-1
No files found.
arch/sh/kernel/setup.c
View file @
c2672f62
...
@@ -307,7 +307,9 @@ static const char *cpu_name[] = {
...
@@ -307,7 +307,9 @@ static const char *cpu_name[] = {
[
CPU_SH7770
]
=
"SH7770"
,
[
CPU_SH7780
]
=
"SH7780"
,
[
CPU_SH7770
]
=
"SH7770"
,
[
CPU_SH7780
]
=
"SH7780"
,
[
CPU_SH7781
]
=
"SH7781"
,
[
CPU_SH7343
]
=
"SH7343"
,
[
CPU_SH7781
]
=
"SH7781"
,
[
CPU_SH7343
]
=
"SH7343"
,
[
CPU_SH7785
]
=
"SH7785"
,
[
CPU_SH7722
]
=
"SH7722"
,
[
CPU_SH7785
]
=
"SH7785"
,
[
CPU_SH7722
]
=
"SH7722"
,
[
CPU_SHX3
]
=
"SH-X3"
,
[
CPU_SH_NONE
]
=
"Unknown"
[
CPU_SHX3
]
=
"SH-X3"
,
[
CPU_SH5_101
]
=
"SH5-101"
,
[
CPU_SH5_103
]
=
"SH5-103"
,
[
CPU_SH_NONE
]
=
"Unknown"
};
};
const
char
*
get_cpu_subtype
(
struct
sh_cpuinfo
*
c
)
const
char
*
get_cpu_subtype
(
struct
sh_cpuinfo
*
c
)
...
...
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