Searched hist:e82da214d2fe3dc2610df966100c4f36bc0fad91 (Results 1 – 6 of 6) sorted by relevance
| /openbmc/linux/arch/sh/kernel/cpu/sh3/ |
| H A D | probe.c | diff e82da214d2fe3dc2610df966100c4f36bc0fad91 Fri Aug 14 20:48:13 CDT 2009 Paul Mundt <lethal@linux-sh.org> sh: Track the CPU family in sh_cpuinfo.
This adds a family member to struct sh_cpuinfo, which allows us to fall
back more on the probe routines to work out what sort of subtype we are
running on. This will be used by the CPU cache initialization code in
order to first do family-level initialization, followed by subtype-level
optimizations.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
|
| /openbmc/linux/arch/sh/kernel/cpu/sh2a/ |
| H A D | probe.c | diff e82da214d2fe3dc2610df966100c4f36bc0fad91 Fri Aug 14 20:48:13 CDT 2009 Paul Mundt <lethal@linux-sh.org> sh: Track the CPU family in sh_cpuinfo.
This adds a family member to struct sh_cpuinfo, which allows us to fall
back more on the probe routines to work out what sort of subtype we are
running on. This will be used by the CPU cache initialization code in
order to first do family-level initialization, followed by subtype-level
optimizations.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
|
| /openbmc/linux/arch/sh/kernel/cpu/sh2/ |
| H A D | probe.c | diff e82da214d2fe3dc2610df966100c4f36bc0fad91 Fri Aug 14 20:48:13 CDT 2009 Paul Mundt <lethal@linux-sh.org> sh: Track the CPU family in sh_cpuinfo.
This adds a family member to struct sh_cpuinfo, which allows us to fall
back more on the probe routines to work out what sort of subtype we are
running on. This will be used by the CPU cache initialization code in
order to first do family-level initialization, followed by subtype-level
optimizations.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
|
| /openbmc/linux/arch/sh/kernel/cpu/sh4/ |
| H A D | probe.c | diff e82da214d2fe3dc2610df966100c4f36bc0fad91 Fri Aug 14 20:48:13 CDT 2009 Paul Mundt <lethal@linux-sh.org> sh: Track the CPU family in sh_cpuinfo.
This adds a family member to struct sh_cpuinfo, which allows us to fall
back more on the probe routines to work out what sort of subtype we are
running on. This will be used by the CPU cache initialization code in
order to first do family-level initialization, followed by subtype-level
optimizations.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
|
| /openbmc/linux/arch/sh/include/asm/ |
| H A D | processor.h | diff e82da214d2fe3dc2610df966100c4f36bc0fad91 Fri Aug 14 20:48:13 CDT 2009 Paul Mundt <lethal@linux-sh.org> sh: Track the CPU family in sh_cpuinfo.
This adds a family member to struct sh_cpuinfo, which allows us to fall
back more on the probe routines to work out what sort of subtype we are
running on. This will be used by the CPU cache initialization code in
order to first do family-level initialization, followed by subtype-level
optimizations.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
|
| /openbmc/linux/arch/sh/kernel/ |
| H A D | setup.c | diff e82da214d2fe3dc2610df966100c4f36bc0fad91 Fri Aug 14 20:48:13 CDT 2009 Paul Mundt <lethal@linux-sh.org> sh: Track the CPU family in sh_cpuinfo.
This adds a family member to struct sh_cpuinfo, which allows us to fall
back more on the probe routines to work out what sort of subtype we are
running on. This will be used by the CPU cache initialization code in
order to first do family-level initialization, followed by subtype-level
optimizations.
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
|