diff options
| author | Paul Mundt <lethal@linux-sh.org> | 2009-04-02 08:40:16 (GMT) |
|---|---|---|
| committer | Paul Mundt <lethal@linux-sh.org> | 2009-04-02 08:40:16 (GMT) |
| commit | e8208828dc014dc0193dc5558995556df0fbe3a5 (patch) | |
| tree | 4cecdf10e8215f65f531af98da1f207712f2e96c /arch/sh/mm | |
| parent | e869a90ee1235a4f89ecb956e7b7d724d65217c8 (diff) | |
| download | linux-e8208828dc014dc0193dc5558995556df0fbe3a5.tar.xz | |
sh: Kill off broken direct-mapped cache mode.
Forcing direct-mapped worked on certain older 2-way set associative
parts, but was always error prone on 4-way parts. As these are the
norm these days, there is not much point in continuing to support this
mode. Most of the folks that used direct-mapped mode generally just
wanted writethrough caching in the first place..
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
Diffstat (limited to 'arch/sh/mm')
| -rw-r--r-- | arch/sh/mm/Kconfig | 12 |
1 files changed, 0 insertions, 12 deletions
diff --git a/arch/sh/mm/Kconfig b/arch/sh/mm/Kconfig index 10c2435..d4079ca 100644 --- a/arch/sh/mm/Kconfig +++ b/arch/sh/mm/Kconfig @@ -251,18 +251,6 @@ config SH7705_CACHE_32KB depends on CPU_SUBTYPE_SH7705 default y -config SH_DIRECT_MAPPED - bool "Use direct-mapped caching" - default n - help - Selecting this option will configure the caches to be direct-mapped, - even if the cache supports a 2 or 4-way mode. This is useful primarily - for debugging on platforms with 2 and 4-way caches (SH7750R/SH7751R, - SH4-202, SH4-501, etc.) - - Turn this option off for platforms that do not have a direct-mapped - cache, and you have no need to run the caches in such a configuration. - choice prompt "Cache mode" default CACHE_WRITEBACK if CPU_SH2A || CPU_SH3 || CPU_SH4 || CPU_SH5 |